Integrated cloud system for premises automation

ABSTRACT

A system comprises premises devices located at a premises. A gateway device is located at the premises and may communicate with the premises devices. A server is configured to interact with the premises devices and the gateway device. A touchscreen device may communicate with the server and configured to interact with the premises devices. The touchscreen device includes a user interface configured to interact with the gateway device. The user interface is configured to control interactions between the premises devices and the gateway device and trigger, based on at least one automation rule, an action of at least one of the premises devices. Corresponding methods, apparatuses and other systems are also provided.

RELATED APPLICATIONS

This application claims the benefit of United States (US) PatentApplication No. 62/186,696, filed Jun. 30, 2015.

This application claims the benefit of U.S. Patent Application No.62/186,825, filed Jun. 30, 2015.

This application claims the benefit of U.S. Patent Application No.62/186,857, filed Jun. 30, 2015.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/189,780, filed Aug. 11, 2008.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/531,757, filed Jun. 25, 2012.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/197,958, filed Aug. 25, 2008.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/334,998, filed Dec. 22, 2011.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/539,537, filed Aug. 11, 2009.

This application is a continuation in part application of U.S. patentapplication Ser. No. 14/645,808, filed Mar. 12, 2015.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/104,932, filed May 10, 2011.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/929,568, filed Jun. 27, 2013.

This application is a continuation in part application of U.S. patentapplication Ser. No. 14/628,651, filed Feb. 23, 2015.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/718,851, filed Dec. 18, 2012.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/972,740, filed Dec. 20, 2010.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/954,553, filed Jul. 30, 2013.

This application is a continuation in part application of U.S. patentapplication Ser. No. 14/943,162, filed Nov. 17, 2015.

This application is a continuation in part application of U.S. patentapplication Ser. No. 15/177,915, filed Jun. 9, 2016.

TECHNICAL FIELD

The embodiments described herein relate generally to networking and,more particularly, to premises automation systems and methods.

BACKGROUND

There is a need for systems and methods that integrate cloud servicesand internet-connected devices with a user interface and othercomponents and functions of a service provider system. This integrationwould enable third party and/or other connected devices (e.g., smartdoor bells, door locks, garage door operators, cameras, thermostats,lighting systems, lighting devices, etc.), and third party services tocontrol or trigger automations in the service provider system usingcomponents and functions of the service provider system. This wouldenable end-users to integrate and use their previously-standaloneinternet-connected devices with each other as well as with their serviceprovider-based service.

INCORPORATION BY REFERENCE

Each patent, patent application, and/or publication mentioned in thisspecification is herein incorporated by reference in its entirety to thesame extent as if each individual patent, patent application, and/orpublication was specifically and individually indicated to beincorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the Integrated Cloud System (ICS) orplatform, under an embodiment.

FIG. 2 is a flow diagram for Service Association, under an embodiment.

FIG. 3 is a flow diagram for Service Disassociation, under anembodiment.

FIG. 4 is a flow diagram for Card UI Interactions, under an embodiment.

FIG. 5 is an example rules interface for controlling triggers andactions involving third party devices integrated in the ICS, under anembodiment.

FIG. 6 is another example of an actions portion of a rules interface forintegrated third party devices, under an embodiment.

FIG. 7 is an example of a triggers portion of a rules interface forthird party services integrated with the ICS, under an embodiment.

FIG. 8 is an example touchscreen display including numerous On states,under an embodiment.

FIG. 9 is an example touchscreen display during arming, under anembodiment.

FIG. 10 is an example touchscreen display including numerous Off states,under an embodiment.

FIG. 11 is an example touchscreen display of a rules list, under anembodiment.

FIG. 12 is an example touchscreen display in response to selection ofthe “Add Rule” icon, under an embodiment.

FIG. 13 is an example touchscreen displayed upon selection of the“Weather Event” icon, including a list of weather events, under anembodiment.

FIG. 14 is an example touchscreen displayed upon selection of the“Reports a temperature” icon, including selections for activating lowand high temperature selections, under an embodiment.

FIG. 15 is an example touchscreen display for selecting a temperaturelimit (lower) for “Reports a temperature” (“choose low”), under anembodiment.

FIG. 16 is an example touchscreen display following selection of atemperature limit (lower) for “Reports a temperature”, under anembodiment.

FIG. 17 is an example touchscreen display for selecting a temperaturelimit (upper) for “Reports a temperature”, under an embodiment.

FIG. 18 is an example touchscreen display following selection of atemperature limit (upper) for “Reports a temperature”, under anembodiment.

FIG. 19 is an example touchscreen display for filtering the temperaturereporting rule based on time or day, under an embodiment.

FIG. 20 is an example touchscreen display for selecting a time afterselecting “any day” as a filtering parameter for the temperaturereporting rule, under an embodiment.

FIG. 21 is an example touchscreen display for selecting system state asan event filter for the temperature repotting rule, under an embodiment.

FIG. 22 is an example touchscreen display for which two arming types areselected for system state as an event filter for the temperaturereporting rule, under an embodiment.

FIG. 23 is an example touchscreen display presenting available actionsfor the temperature reporting rule, under an embodiment.

FIG. 24 is an example touchscreen display for selecting a type of deviceto control in response to choosing an action to control a deviceaccording to a temperature reporting rule, under an embodiment.

FIG. 25 is an example touchscreen display for displaying a list ofdevice types corresponding to the selected device type to be controlledunder the temperature reporting rule, under an embodiment.

FIG. 26 is an example touchscreen display showing selection of aparticular ceiling fan device (“Patio”) under the temperature reportingrule, under an embodiment.

FIG. 27 is an example touchscreen display showing available actions ofthe selected device for control under the temperature reporting rule,under an embodiment.

FIG. 28 is an example touchscreen display showing options for creating acompound rule with additional actions, under an embodiment.

FIG. 29 is an example touchscreen display for saving a rule, under anembodiment.

FIG. 30 is an example touchscreen display of a rules list followingcreation of a new rule, under an embodiment.

FIG. 31 is an example touchscreen display of a rules list, under anembodiment.

FIG. 32 is an example touchscreen display in response to selection ofthe “Add Rule” icon, under an embodiment.

FIG. 33 is an example touchscreen displayed upon selection of the“Irrigation” icon, including a list of irrigation events, under anembodiment.

FIG. 34 is an example touchscreen displayed upon selection of the“Switches on” icon, including selections for a day for the switchingevent, under an embodiment.

FIG. 35 is an example touchscreen display for selecting an “on” timeafter selecting “any day” as a filtering parameter for the switchingevent, under an embodiment.

FIG. 36 is an example touchscreen display for selecting a time of day asa start time, under an embodiment.

FIG. 37 is an example touchscreen display following selection of a starttime for the switching event rule, under an embodiment.

FIG. 38 is an example touchscreen display for selecting a time of day asan end time, under an embodiment.

FIG. 39 is an example touchscreen display following selection of a starttime and an end time for the switching event rule, under an embodiment.

FIG. 40 is an example touchscreen display for selecting system state asan event filter for the switching event rule, under an embodiment.

FIG. 41 is an example touchscreen display presenting available actionsfor the switching event rule, under an embodiment.

FIG. 42 is an example touchscreen display for selecting a type of deviceto control in response to choosing an action for the switching eventrule, under an embodiment.

FIG. 43 is an example touchscreen display for displaying a list ofdevice types corresponding to the selected device type (“lights”) to becontrolled under the switching event rule, under an embodiment.

FIG. 44 is an example touchscreen display showing selection ofparticular lighting devices (“Porch” and “Living Room”) under theswitching event rule, under an embodiment.

FIG. 45 is an example touchscreen display showing available actions ofthe selected device (“Porch light”) for control under the switchingevent rule, under an embodiment.

FIG. 46 is an example touchscreen display showing available actions ofanother selected device (“Living Room light”) for control under theswitching event rule, under an embodiment.

FIG. 47 is an example touchscreen display showing options for creating acompound rule with additional actions under the switching event rule,under an embodiment.

FIG. 48 is an example touchscreen display for selecting a type of deviceto control in response to choosing an additional control device for acompound switching event rule, under an embodiment.

FIG. 49 is an example touchscreen display for displaying a list ofdevice types corresponding to the selected device type (“shades”) to becontrolled under the compound switching event rule, under an embodiment.

FIG. 50 is an example touchscreen display showing available actions ofthe selected device (“Living room shades”) for control under thecompound switching event rule, under an embodiment.

FIG. 51 is an example touchscreen display for saving a rule, under anembodiment.

FIG. 52 is an example touchscreen display of a rules list followingcreation of the new switching event rule, under an embodiment.

FIG. 53 is a flow diagram for local card development and unit testing,under an embodiment.

FIG. 54 is a flow diagram for card integration testing, under anembodiment.

FIG. 55 is a flow diagram for card production, under an embodiment.

FIG. 56 is an example card (e.g., thermostat, etc.) operating on a smartphone, under an embodiment.

FIG. 57 is an example small card (e.g., thermostat, etc.), under anembodiment.

FIG. 58 is an example card menu, under an embodiment.

FIG. 59 is a block diagram of the integrated security system, under anembodiment.

FIG. 60 is a block diagram of components of the integrated securitysystem, under an embodiment.

FIG. 61 is a block diagram of the gateway software or applications,under an embodiment.

FIG. 62 is a block diagram of the gateway components, under anembodiment.

FIG. 63 is a block diagram of IP device integration with a premisenetwork, under an embodiment.

FIG. 64 is a block diagram of IP device integration with a premisenetwork, under an alternative embodiment.

FIG. 65 is a block diagram of a touchscreen, under an embodiment.

FIG. 66 is an example screenshot of a networked security touchscreen,under an embodiment.

FIG. 67 is a block diagram of network or premise device integration witha premise network, under an embodiment.

FIG. 68 is a block diagram of network or premise device integration witha premise network, under an alternative embodiment.

FIG. 69 is a flow diagram for a method of forming a security networkincluding integrated security system components, under an embodiment.

FIG. 70 is a flow diagram for a method of forming a security networkincluding integrated security system components and network devices,under an embodiment.

FIG. 71 is a flow diagram for installation of an IP device into aprivate network environment, under an embodiment.

FIG. 72 is a block diagram showing communications among IP devices ofthe private network environment, under an embodiment.

FIG. 73 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment.

FIG. 74 is a block diagram of an integrated security system wirelesslyinterfacing to proprietary security systems, under an embodiment.

FIG. 75 is a flow diagram for wirelessly ‘learning’ the gateway into anexisting security system and discovering extant sensors, under anembodiment.

FIG. 76 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel wirelessly coupled to agateway, under an embodiment.

FIG. 77 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel wirelessly coupled to agateway, and a touchscreen, under an alternative embodiment.

FIG. 78 is a block diagram of a security system in which the legacypanel is replaced with a wireless security panel connected to a gatewayvia an Ethernet coupling, under another alternative embodiment.

FIG. 79 is a flow diagram for automatic takeover of a security system,under an embodiment.

FIG. 80 is a flow diagram for automatic takeover of a security system,under an alternative embodiment.

FIG. 81 is a general flow diagram for IP video control, under anembodiment.

FIG. 82 is a block diagram showing camera tunneling, under anembodiment.

DETAILED DESCRIPTION

Systems and methods comprise premises equipment including premisesdevices located at a premises. A partner device is located at thepremises and configured to use a partner protocol different from aprotocol of the premises equipment. A system server is configured tointeract with the premises devices and the partner device. A userinterface is coupled to the system server and configured to interactwith the premises devices. The user interface includes a partner userinterface corresponding to the partner device. The partner userinterface configures the user interface to interact with the partnerdevice. The user interface is configured to control interactions betweenthe premises devices and the partner device.

Embodiments also include systems and methods comprising premisesequipment including premises devices located at a premises. The systemincludes a partner device located at the premises and configured to usea partner protocol different from a protocol of the premises equipment.The system includes a system server configured to interact with thepremises devices. The system server is configured to interact with thepartner device via a partner proxy corresponding to the partner device.The system includes automation rules coupled to the system server. Theautomation rules include actions and triggers for controllinginteractions between at least one of the partner device and the premisesdevices. The system includes a user interface coupled to the systemserver and configured to interact with the premises devices and thepartner device.

FIG. 1 is a block diagram of the integrated cloud system or platform 70,under an embodiment. The integrated cloud system (ICS) of an embodimentcomprises cloud-based components that include a Cloud IntegrationService/Server (CIS) 5 coupled to a system server 7 (e.g., “IcontrolServer”, also referred to herein as the service provider server) via aninternal event bus 9. The CIS 5 system server 7 and event bus 9 areimplemented by the service provider in data centers of the serviceprovider's customers, but are not so limited.

The system server is coupled to customer-premises equipment (CPE) atcorresponding subscriber premises of numerous subscribers. The CPEincludes one or more of security panels, security systems, gateways,hubs, touchscreens, and Wi-Fi access points that operate as a gateway tothe system servers and ICS. The CPE is described in detail in theRelated Applications incorporated by reference herein.

The CIS is coupled to a partner's production server (“partner server”)via a Cloud Integration Adapter (CIA). The partner server interacts withtheir products/services that their users wish to integrate into theirICS platform. The Cloud Integration Adapter provides the system serverand CIS with REST endpoints to call for checking the health of theadapter, associating with adapter cloud devices, and processing eventscoming from the CIS. Furthermore, the Cloud Integration Adapter isresponsible for sending events to the CIS as acknowledgement of incomingsystem events, and as an endpoint for Adapter managed cloud deviceevents to be reported into the system servers.

The ICS of an embodiment effects integration of cloud services andinternet-connected devices with the user interface, Rules Engine andother components and functions of the service provider system. Thisintegration enables third party and/or other connected devices (e.g.,smart door bells (e.g, Doorbot, etc.), door locks, garage door operators(e.g., Chamberlain, etc.), cameras (e.g., Dropcam, etc.), thermostats(e.g., Nest, etc.), lighting systems (e.g., Philips Hue, etc.), lightingdevices, lawn irrigation systems (e.g., Rachio, etc.), plant sensors,pet feeders, weather stations, rain sensors, pool controls, air qualitysensors, music systems, remote controllers, internet user interfaces,connected systems, connected vehicles, etc.), and third party services(e.g., weather forecasting services and applications (e.g., Accuweather,etc.), family networking services and applications, partner or thirdparty services, Accuweather, MSO digital assets such as voicemail,etc.), to control or trigger automations in the service provider systemusing the user interface, Rules Engine and other components andfunctions of the service provider system. This enables end-users tointegrate and use their previously-standalone internet-connected deviceswith each other as well as with their service provider-based service.

The ICS of an embodiment as described in detail herein includes one ormore components of the “integrated security system” described in detailin the Related Applications, which are incorporated by reference herein.An example of the “integrated security system” is available as one ormore of the numerous systems or platforms available from iControlNetworks, Inc., Redwood City, Calif. The ICS of an embodimentincorporates one or more components of the “integrated security system”.The ICS of an embodiment is coupled to one or more components of the“integrated security system”. The ICS of an embodiment integrates withone or more components of the “integrated security system”.

The system server includes or hosts a partner proxy and an integrationREST application programming interface (API). The integration REST APIis coupled to the CIS. The partner proxy is coupled to a correspondingpartner server, and is also coupled to a Card UI (“REST Client”). Thepartner proxy is configured to proxy API calls from the Partner's CardUI (REST client) to the Partner Server and appends the appropriate OAuthToken for a given user. This enables all client UIs to be enabled aftera single OAuth pairing is completed (i.e., if one user authorizesPartner's product, all users and clients on the same account will haveit auto-enabled and populated). This also improves security by notstoring the user's credentials on the Partner's server in the client UI.The Card UI of an example embodiment is an HTML5-based user interfacecard developed by the Partner, or service provider, that is embeddedinto the service provider user interface (e.g., mobile app, web portal).

The ICS of an embodiment includes Cloud Actions and Triggers (CAT),which enable third party connected devices and services to triggerautomations in the service provider system, thereby enabling end-usersto integrate and use their previously-standalone internet connecteddevices with their service provider-based service.

Devices and services that are hosted outside of the automation platformor network are referred to as ‘cloud objects’ and provide numerous usecases when integrated with the system of an embodiment. The descriptionthat follows includes details of aspects of the system including but notlimited to server infrastructure required to support external cloudobjects, data format definitions for actions and triggers across theevent bus, the process of onboarding external cloud objects, integrationof cloud objects with the CPE rules engine, common OAuth2 Support forCloud Services, and card UI/SDK Support for Cloud Objects.

The CAT of an embodiment integrates partner services into the ICSplatform including support for rules on the CPE and partner-specificuser interfaces based on the Card UI. The system of an embodimentincludes a web API for the CIS for which partners develop IntegrationAdapters (also referred to as “adapters”) responsible for thetranslation of service provider events and operations into partnerproprietary calls. Partners also develop Cards with the Card SDK inorder to get branded partner specific user interfaces. The partners ofan embodiment host their Integration Adapters in their environments,however in an alternative embodiment the adapters are hosed by the ICSdescribed herein.

While the rules engine of an embodiment is included and running on CPE,the embodiments herein are not so limited. In an alternative embodimentthe rules engine is included and running on a system server or othercomponent of the ICS platform.

In another alternative embodiment the rules engine is distributedbetween the CPE and ICS platform so that a set of rules is included andrunning on the CPE while another set of rules is included and running onthe ICS platform. For example, rules controlling actions and triggerslimited to local devices in the premises, and not using any data orinformation from a device or service outside the premises, are includedand running on the CPE. Likewise, rules controlling actions and triggersinvolving device(s) in the premises, and also involving device(s) orservice(s) outside the premises, are included and running on the CPE.

The CAT includes but is not limited to use cases comprising ServiceAssociation, Cloud Object Creation, Service Disassociation, Cloud ObjectSynchronization, Card UI Interactions, Rule Authoring, and RuleExecution. Each of the use cases is described in detail herein.

Upon startup, the Partner's Cloud Integration Adapter uses username,password and partnerKey to authenticate with the CIS. The username,password and partnerKey are provided by the service provider. ThePartner's Event Callback URL and Health Check URL are defined initiallyas part of the partner onboarding process. The CIS provides two URLs forthe partner to optionally update the two URLs at runtime.

The Register Event callback URI allows partner to update the EventCallback URL at runtime.

Endpoint/cloudIntegration/[partnerName]/eventCallback/registerEventCallback?partnerUrl=[partnerUrl] Description Update the eventCallback URL for a partnerMethod POST Header x-login - username of the integration userx-password - password of the integration user x-partnerKey - unique keyissued by Service provider to the partner URL partnerName: The uniquename of the partner provided by Service provider parameters partnerUrl:The updated Event Callback URL Result HTTP response 200 if successful

An example payload includes but is not limited to the following:

curl -k -L -v -H “X-login: <username>” -H “X-password: test” -H“x-partnerKey: key” - X POST“https://<server>/cloudIntegration/icontrol/cloudIntegrations/rachio/eventCallback/registerEventCallback?partnerUrl=https://rachioAdapter/updatedEventCallbackUrl”

The Register Health Check Callback URI allows partner to update theHealth Check URL at runtime.

Endpoint/cloudIntegration/[partnerName]/healthCheckCallback/registerHealthCheckCallback?partnerHealthCheckUrl=[partnerHealthCheckUrl] Description UpdatehealthCheckCallback URL for partner Method POST Header x-login -username of the integration userx-password - password of the integrationuserx-partnerKey- A unique key issued by Service provider to the partnerURL partnerName: The unique name of the partnerpartner parametersHealthCheckUrl: The updated health check URL Result HTTP response 200 ifsuccessful

An example payload includes but is not limited to the following:

curl -k -L -v -H “Content-Type: text/xml ” -H “X-login: <username>” -H“X-password: test” -H “x-partnerKey: key” -X POSThttps://<server>/cloudIntegration/icontrol/cloudIntegrations/rachio/healthCheckCallback/registerHealthCheckCallback?partnerHealthCheckUrl=https://rachioAdapter/updatedHealthcheckcallback.

For both the Event Callback Registration and Health Check CallbackRegistration, the CIS responds with a HTTP 200 if the POST is accepted.Appropriate HTTP error code will be returned for error conditions.

The Health Check Callback service implemented by the Partner supportsHTTP GET operations, and responds with HTTP 200 to indicate all systemsare functioning properly. Any other response will be considered anindication that the adapter is not available. The CIS of an embodimentperiodically checks availability of the Integration Adapter, and theperiodicity is configurable.

The cloud integration user lifecycle of an embodiment embodies the coreuser experiences from a technical viewpoint (i.e., technical use cases).The following user lifecycle use cases are described in detail herein:Service Association (User Onboarding); Updating new userproduct(s)/service(s) on the Partner's server; Product/Service statusupdates; Controlling user's product(s)/service(s) from the serviceprovider platform; User Offboarding of one or moreproduct(s)/service(s).

Service Association (User Onboarding) is initiated by the user via aservice provider user interface when the user selects a Partner devicetype from the list of devices available to pair to the user's Serviceprovider system. FIG. 2 is a flow diagram 11 for Service Association,under an embodiment. Service Association (Partner Onboarding) isinitiated by a Card UI 13 of an embodiment when the user selects apartner from a partner list. The list of all possible partners and theircustom (partner specific) cards are built into each release of the CardUI (they are not dynamically downloaded from a server). However the listof enabled partners (and related metadata) is dynamically retrieved fromService provider server 15 (also referred to herein as Icontrol Server15) via an API.

Once the user selects a partner service for association, three-leggedOAuth2 begins. A browser control is created, has its context populatedwith information identifying the user, and calls Service provider OAUTHRedirect servlet, which in turn opens the OAuth2 landing page URL withthe required parameters (response_type, client_id and token). This page,served by the partner's web server 17 (also referred to herein asPartner Server 17), collects the user's ID and password and successfullyauthenticates.

After the user is authenticated, the partner server issues an HTTP 302redirect to the Service provider OAuth Callback servlet located in theportal server and includes an authorization code as well as the rest ofthe original browser context. The OAuth Callback servlet contacts thepartner's service to exchange the authorization code for an access tokenwhich it stores in the database.

Then, the OAuth Callback servlet will call the ‘Associate Account URL’provided by the partner. The access token for the user account isattached to the request as the Authorization header to identify theuser. The response to the call will include the user's account id in thepartner system and a list of cloud devices owned by the user. Aftersuccessful account association, HTTP 200 is returned to the browserindicating the completion of the service association process.

The service provider OAUTH callback URL has the following format, but isnot so limited: https://<servername>/oauth/oauthPartner/<partnerName>.It is recommended that a service provider deployment registers this URLin the partner's system. As an alternate (less secure) option, this URLcan be passed to the partner system as a parameter in the first leg ofthe OAUTH process.

The system of an embodiment includes Cloud Object Synchronization asdescribed herein. After a service has been associated for auser/account, the system server has the list of cloud devices owned bythe user. If the user adds/removes a device in the partner's system,partner server calls the Service provider Cloud Integration Service APIto inform Service provider regarding the change. Conversely, if userremoves a cloud device association in Service provider Card UI, an eventwill be sent to the partner's system via the ‘Event Callback URL’.

After completing user authentication, the OAuth token for the useraccount is attached to a request to associate the account (AssociateAccount in FIG. 2). The Partner Server's 17 response to the call willinclude the user's Account ID in the Partner's system and a list ofcloud-enabled devices owned by the user in that account. Aftersuccessful account association, HTTP 200 is returned to the browserindicating the completion of the service association process. After aservice has been associated for a user/account, the Service providerserver 15 will have the list of cloud devices owned by the user.

Account association with the CIS is the process by which the systemserver creates the relationship between the Service provider user andpartner cloud devices. The Cloud Integration Service sends, via HTTPPOST, a JSON Object containing the OAuth Access Token.

An example Associate Account Request follows but the embodiment is notso limited:

URL The ‘Associate Account URL’ provided by the partner in the CloudIntegration Submission Form. Description Get the user's account/deviceinfo from the partner. Method POST Header Authorization - ‘Bearer xxxxx’where xxxxx is the user's access token. URL customerName: The name ofthe Service provider server. parameters

When an account association request is received by the Cloud IntegrationAdapter, it responds with a JSON message in the following format:

Associate Account Response { “virtualDevice.siteId”:“acc_1234”,“virtualDevice.instanceIds”:[ { “id”:“device-inst001”, “name”:“FrontSprinkler” }, { “id”:“device-inst002”, “name”:“Backyard Sprinkler” } ] }Where:

Field Name Description virtualDevice.siteId The user ID in the Partner'ssystem. This will be the global identifier used by Service provider torefer to the Partner's primary user. virtualDevice.instanceIds A list(JSON Array) of devices the Partner or user wishes Service provider tointeract with. id The Device ID in the Partner's system. name A friendlydisplay name for this device.

A HTTP 200 is expected along with this data. Error codes should includean HTTP 500 for errors, and an HTTP 401 for improper OAuth token.

Updating status of partner product (events) involves user's interactingwith the Partner's product/service through a Partner client (e.g.,Partner mobile app) or the user may interact with the device locally andchange its state, mode, or otherwise affect the product/service'sstatus. Events received from the Partner's Cloud Integration Adapter canbe treated as a trigger for a rule in the Service provider system (e.g.,when the backyard sprinkler system is running, lock the pet door).

An example payload description follows but the embodiment is not solimited:

Endpoint /cloudIntegration/[partnerName]/events/submitCloudEventDescription Submit partner events to Service provider server. MethodPOST Header x-login - username of the integration user.x-password -password of the integration user.x-partnerKey- A unique key issued byService provider to the partner URL partnerName: The unique name of thepartner.externalAccountId: The user's parameters account ID in thepartner system. Events originated from the partner system in IcEvent(s)JSONformat.Example:{“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“name”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.providerId”,“value”:“rachio”}],“mediaType”:“sprinkler/on”,“ts”:1409675025053,“value”:“true”}]}

Fields:

-   -   mediaType: The event mediaTypes defined as part of the cloud        object Body definition and approved by Service provider.    -   ts: The time when the event happened (in milliseconds).

Event Metadata:

-   -   virtualDevice.providerId: The name of the partner. Also referred        to as Integration_ID in the Card SDK.    -   virtualDevice.siteId: The user's account ID in the partner        system.    -   virtualDevice.instanceId: The device ID in the partner system.        Result HTTP response 200 if successful.

In controlling a partner product via the rules engine (actions) of anembodiment, the CIS uses the partner's Event Callback URL to submitaction events to partner's system. Typically, an action event asks tothe partner's system to perform a specific function. The partner submitsthe result of the action back to Service provider in the form of anevent.

Payload Description URL The Event Callback URL for the partnerDescription Submit action events to partner server. Method POST HeaderAuthorization - The value is ‘Bearer xxxxxx’ with xxxxxx being theuser's OAUTH access token.externalAccountId: The user's account ID inthe partner system (to be added on Padre release). URL parameters None.Action events originated from the Service provider system in IcEventJSON format. Example event sent to Rachio:

{“icEvent”:[{“ts”:1409675025053,“instanceId”:“181964.0”,“mediaType”:“virtualDevice/pending”,“id”:“1430834677258”,“instanceName”:“Bedroom”,“value”:null,“context”:[ ],“metaData”:“name”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“name”:“virtualDevice.providerId”,“value”:“rachio”},{“name”:“functionMediaType”,“value”:“sprinkler/schedulePause”},{“requestMessageId”,“value”:“1430489036”}]}]}Fields:

-   -   id: The event ID generated by Service provider server.    -   mediaType: All action events have ‘virtualDevice/pending’ as the        event media type. The actual action is represented as        ‘sprinkler/schedulePause’ in metadata.        Body    -   ts: The time when the event happened (in milliseconds).    -   instanceId: The ID of the device in Service provider system.        Event Metadata:    -   virtualDevice.providerId: The name of the partner. Also referred        to as Integration_ID in the Card SDK.    -   virtualDevice.siteId: The user's account ID in the partner        system.    -   virtualDevice.instanceId: The device ID in the partner system.    -   functionMediaType: Identifies the action called by Service        provider. The list of all possible function media types are        defined at the time of partner onboarding.    -   requestMessageId: The ID of the action request. Partner should        used the this ID when sending success/failure response.        Upon receiving the action event, partner should send        success/failure response as event to Service provider server.

Action Successful response: Event{“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“naResponse me”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.providerId”,“value”:“rachio”},,{“name”:“requestMessageId”,“value”:“1430489036”}],“mediaType”:“virtualDevice/success”,“ts”:1409675025053,“value”:“true”}]} Failure Response:{“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“name”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.providerId”,“value”:“rachio”},,{“name”:“requestMessageId”,“value”:“1430489036”}],“mediaType”:“virtualDevice/failed”,“ts”:1409675025053,“errorCode”:“500”,“value”:“true”}]}

Event disposition is determined by the functionMediaType in the metaDataarray. In the above example, the functionMediaType has the value ofdevice/schedulePause, but depending on the function, there may be aparameter or value in order to effect the desired control.

FIG. 3 is a flow diagram 72 for Service Disassociation, under anembodiment. If the user adds/removes a device in the Partner's system,the Partner Server 17 calls the CIS API to inform Service provider aboutthe change. A Cloud Service 6 can be disassociated from an Serviceprovider user through an API invocation on the Service provider server15. This removes the cloud account and its associated Cloud devices fromthe Service provider server. A SMAP message is sent to the CPE 4 toupdate its Cloud Object inventory, and the CIS calls the partner's‘Event Callback URL’ to inform the Partner that the user hasdisassociated.

Payload Description URL The Event Callback URL for the partnerDescription Notify Partner Server that a user has “deleted” or removedone of their partner products from being controlled by the Serviceprovider system. Method POST URL None Parameters Body { “icEvent”:[ {“metaData”:[ { “name”:“virtualDevice.siteId”,“value”:“rachio-account-id-0001”, }, {“name”:“virtualDevice.instanceId”, “value”:“rachio-userinst-0001”, }, {“name”:“virtualDevice.providerId”, “value”:“rachio”, }, ],“id”:“1409865500000”, “mediaType”:“virtualDevice/remove”,“ts”:1409865500000, “href”:“sites/1/network/instances/181002.0”,“siteId”:“1”, “deviceId”:“1002”, “instanceId”:“181002.0”, } ] }

Event metadata includes but is not limited to: virtualDevice.providerId(e.g., name of the partner, also referred to as Integration_ID in theCard SDK); virtualDevice.siteId (e.g., user's account ID in the partnersystem); virtualDevice.instanceId (e.g., device ID in the partnersystem). Fields include but are not limited to: mediaType (e.g., allremove events will have a mediaType of ‘virtualDevice/remove’); ts(e.g., time when the event happened (in milliseconds)); instanceId(e.g., ID of the device in Service provider system); id (e.g., event IDgenerated by Service provider server).

FIG. 4 is a flow diagram 8 for Card UI Interactions, under anembodiment. The Card UIs that interact with the Cloud Objects will notdepend on data stored in Service provider servers. Instead the cardswill interact through the Partner Proxy Service 10, which handlesauthentication and logging, to make calls to the partner server 17. Forexample, a Nest card that needs to show a list of thermostats will getthe list of thermostats and their metadata indirectly from Nest (throughthe Partner Proxy Service 10) instead of leveraging the Cloud Objectdata stored in our database. This is done primarily due to the desire tohave the Card UI authors, which are expected to be the partnersthemselves, use their own APIs for easier development. Note that it doesprovide the possibility for the two data sets (the Cloud Objects in ourdatabase and the list of devices provided by the partner's server) toget out of sync if bugs exist in the integrations. Normally changesshould be synchronized as described above in Cloud ObjectSynchronization and the two data sets should be equivalent.

Cards will be oblivious to authentication with the Partner Server(except for service association where the authentication data is storedin our server). Invocations to the Partner Proxy Service cause it toattempt a ‘pass-through’ invocation on the Partner Server using theauthentication credentials stored in the database. If the Partner Serverresponds with a 401 authentication failure, the Partner Proxy Servicewill attempt to refresh the token and re-attempt the invocation to thePartner Server with the updated token as shown in the diagram above.Authentication credentials are not made available to the Cards, so theyperform authenticated requests through the Partner Proxy Service.

The system of an embodiment includes files that form the CloudIntegration Metadata. As an example, an embodiment includes CloudIntegration Descriptor (CID) and Rules Template files that make up theCloud Integration Metadata that defines a cloud integration.

The CID describes the capabilities of the devices and/or servicesprovided by the Partner Provider Plugin including attributes, actions,events, and their associated parameters. This descriptor is used by theserver to provide REST API access to the capabilities provided by thecloud service, but is not so limited.

An example CID XSD of an embodiment is as follows, but the embodiment isnot so limited.

CID XSD <xs:complexType name=“cloudObject”> <xs:complexContent><xs:sequence> <xs:element name=“name” type=“xs:token”/> <xs:elementname=“metaData” type=“metaData” minOccurs=“0” maxOccurs=“64”/><xs:element name=“point” type=“point” minOccurs=“0” maxOccurs=“64”/><xs:element name=“function” type=“function” minOccurs=“0”maxOccurs=“64”/> </xs:sequence> <xs:attribute name=“id” type=“xs:string”use=“required”/> <xs:attribute name=“mediaType” type=“xs:token”use=“optional”/> <xs:attribute name=“href” type=“xs:anyURI”/><xs:attribute name=“tags” type=“xs:token”/> <xs:attribute name=“status”type=“cloudObjectStatus”/> </xs:complexContent> </xs:complexType><xs:complexType name=“metaData”> <xs:attribute name=“name”type=“xs:string”/> <xs:attribute name=“value” type=“xs:string”/><xs:attribute name=“mediaType” type=“xs:token”/> </xs:complexType><xs:complexType name=“point”> <xs:attribute name=“mediaType”type=“xs:token” use=“required”/> <xs:attribute name=“name”type=“xs:string”/> <xs:attribute name=“href type=“xs:anyURI”/><xs:attribute name=“value” type=“xs:string”/> <xs:attribute name=“ts”type=“xs:long”/> <xs:attribute name=“readOnly” type=“xs:boolean”use=“required”/> </xs:complexType> <xs:complexType name=“function”><xs:sequence> <xs:element name=“input” type=“input” minOccurs=“0”maxOccurs=“unbounded”/> </xs:sequence> <xs:attribute name=“mediaType”type=“xs:token” use=“required”/> <xs:attribute name=“name”type=“xs:token”/> <xs:attribute name=“href” type=“xs:anyURI”/><xs:attribute name=“description” type=“xs:string”/> </xs:complexType><xs:simpleType name=“cloudObjectStatus”> <xs:restrictionbase=“xs:token”> <xs:enumeration value=“ok”/> <xs:enumerationvalue=“offline”/> <xs:enumeration value=“unknown”/> <xs:enumerationvalue=“missing”/> <xs:enumeration value=“searching”/> <xs:enumerationvalue=“configuration_failure”/> <xs:enumeration value=“upgrading”/><xs:enumeration value=“configuring”/> </xs:restriction> </xs:simpleType>

An example CID of an embodiment is as follows, but the embodiment is notso limited.

Example CID

<Nest id=“Nest343234345” mediaType=“cloud/nest” tags=“thermostat”status=“ok”> <name>My Nest</name> <metadata name=“manufacturer”mediaType=“cloud/nest/manufacturer” value=“Nest”/> <metadataname=“model” mediaType=“cloud/nest/model” value=“M1”/> <pointname=“temperature” mediaType=“cloud/nest/temperature” value=“2800”ts=“23434535464557” readOnly=“false”/> <point name=“coolSetpoint”mediaType=“cloud/nest/coolSetpoint” value=“2400” ts=“23434535464557”readOnly=“false”/> <point name=“heatSetpoint”mediaType=“cloud/nest/heatSetpoint” value=“2000” ts=“23434535464557”readOnly=“false”/> <function name=“resetSetpoints”mediaType=“cloud/nest/reset” description=“reset heat/cool setpoint tofactory default”/> </Nest>

An example Rules XSD Changes of an embodiment is as follows, but theembodiment is not so limited.

Rules XSD Changes

<!-- - Subclass of trigger for Cloud commands. --> <xsd:complexTypename=“cloudTrigger”> <xsd:complexContent> <xsd:extension base=“trigger”><xsd:sequence> <!-- - The specific cloud object ID. --> <xsd:elementname=“cloudObjectID” type=“xsd:string” minOccurs=“1” maxOccurs=“1”/><!-- the evaluation mechanism to apply to this trigger --> <xsd:choice><xsd:element name=“simpleEval” type=“cloudSimpleTriggerEvaluation”/><xsd:element name=“comparisonEval”type=“cloudComparisonTriggerEvaluation”/> </xsd:choice> </xsd:sequence></xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:elementname=“cloudTrigger” type=“cloudTrigger” substitutionGroup=“trigger”/><!-- simple cloud trigger evaluation (just an event, no args) --><xsd:complexType name=“cloudSimpleTriggerEvaluation”> <xsd:sequence><xsd:element name=“eventName” type=“xsd:string”/> </xsd:sequence></xsd:complexType> <!-- cloud trigger evaluation that compares a value--> <xsd:complexType name=“cloudComparisonTriggerEvaluation”><xsd:sequence> <xsd:element name=“attributeName” type=“xsd:string”/><xsd:element name=“comparisonMethod” type=“comparisonMethodEnum”/><xsd:element name=“comparisonValue” type=“xsd:double”/> </xsd:sequence></xsd:complexType> <!-- comparison methods --> <xsd:simpleTypename=“comparisonMethodEnum”> <xsd:restriction base=“xsd:string”> <!--equality --> <xsd:enumeration value=“eq”/> <!-- less than --><xsd:enumeration value=“lt”/> <!-- less than or equal --><xsd:enumeration value=“le”/> <!-- greater than --> <xsd:enumerationvalue=“gt”/> <!-- greater than or equal --> <xsd:enumerationvalue=“ge”/> </xsd:restriction>  </xsd:simpleType>

An example Master Action List Changes of an embodiment is as follows,but the embodiment is not so limited.

Master Action List Changes

<a:action actionID=“137”> <a:description>Invoke a CloudAction</a:description> <a:parameterDef> <a:key>cloudObjectID</a:key><a:type>string</a:type> </a:parameterDef> <a:parameterDef><a:key>cloudActionID</a:key> <a:type>string</a:type> </a:parameterDef><a:parameterDef> <a:key>parameters</a:key> <a:type>string</a:type> <!--a JSONArray of JSONObjects that contain name/value/type triplets (typeis optional) --> </a:parameterDef> <!-- does this type make sense? --><a:type>workflow</a:type> <a:target>ruleAction_invokeCloud</a:target> </a:action>

An example Rule XML Examples of an embodiment is as follows, but theembodiment is not so limited.

Rule XML Examples

<rule ruleID=“1002351”> <triggerList> <cloudTrigger> <description>CloudTrigger</description> <category>cloud</category> <!-- just points to theglobal service, not to any particular instance --><cloudObjectID>AccuWeather</cloudObjectID> <!-- it is assumed here thatwhen the AccuWeather account is connected that it is already filteringbased on the user's location / zipcode --> <simpleEval><eventName>tornadoWarning</eventName> </simpleEval> </cloudTrigger></triggerList> <action> <actionID>70</actionID> <parameter><key>lightID</key> <value>3781220513309696</value> </parameter><parameter> <key>level</key> <value>100</value> </parameter> </action><description>Turn on kitchen light when Tornado Warning</description></rule>  <rule ruleID=“1008603”> <triggerList> <zoneTrigger><description>Zone Trigger</description> <category>sensor</category><zoneState>open</zoneState> <zoneID>18</zoneID> </zoneTrigger></triggerList> <action> <actionID>137</actionID> <parameter><key>cloudObjectID</key> <value>nest.1</value> <!-- device 1 under thenest service associated with this account --> </parameter> <parameter><key>cloudActionID</key> <value>configureThermostat</value> </parameter><parameter> <key>parameters</key> <value>[ { “name”: “heatSetPoint”,“value”: “2200”, “type”: “nest/temperature” }, { “name”: “coolSetPoint”,“value”: “2700” } ] </value> </parameter> </action> <description>Zone 1Open Configure Nest Thermostat</description> </rule>

In order to provide a dynamic list of available actions and triggersduring rule authoring, templates describing the available functionalitymust be provided with the Cloud Integration Metadata. Some examples oftrigger and action templates (e.g., Rachio Smart Sprinkler Controllertrigger and action template, AccuWeather weather service triggertemplate, etc.) of an embodiment are as follows, but the embodiment isnot so limited.

Example Rule Templates

<rules-core:triggerTemplates xmlns:rules-core=“rules-core”xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”xsi:schemaLocation=“rules-core../../../../rules-core/src/main/resources/rules- core.xsd”><rules-core:triggerTemplate id=“203”description=“{STR.RULES.TEMPLATES.TRIGGER.DESC.INSTANCE.RAC HIO}”cvTriggerType=“cloudTrigger” cvCategory=“cloud”excludeActionIds=“10:11:15:16:17:18:100:101:103:120:121:122:135:136:137:138:139”> <rules-core:inputs> <rules-core:input hidden=“false”description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.DES C.RACHIO}”name=“targetValues” pattern=“eq”> <optiondescription=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPTION.DESC.RACHIO.ON}” value=“1” /> <optiondescription=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPTION.DESC.RACHIO.OFF}” value=“0” /> </rules-core:input> <rules-core:inputhidden=“true” name=“type” value=“event” /> <rules-core:inputhidden=“false” name=“instanceIds” /> <rules-core:input hidden=“true”name=“tags” value=“rachio” /> <rules-core:input hidden=“true”name=“mediaTypes” value=“sprinkler/on” /> </rules-core:inputs></rules-core:triggerTemplate> </rules-core:triggerTemplates><rules-core:triggerTemplates xmlns:rules-core=“rules-core”xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”xsi:schemaLocation=“rules-core../../../../rules-core/src/main/resources/rules- core.xsd”><rules-core:triggerTemplate id=“200”description=“{STR.RULES.TEMPLATES.TRIGGER.DESC.INSTANCE.ACC UWEATHER}”cvTriggerType=“cloudTrigger” cvCategory=“cloud”excludeActionIds=“10:11:15:16:17:18:135:136”> <rules-core:inputs><rules-core:input hidden=“false”description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.DESC.ACCUWEATHER}” name=“targetValues” pattern=“gt”> <optiondescription=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPTION.DESC.ACCUWEATHER.TEMPERATURE.GT}” value=“temperatureGt” /></rules-core:input> <rules-core:input hidden=“true” name=“type”value=“event” /> <rules-core:input hidden=“false” name=“instanceIds” /><rules-core:input hidden=“true” name=“tags” value=“accuWeather” /><rules-core:input hidden=“true” name=“mediaTypes”value=“weather/temperature” /> </rules-core:inputs></rules-core:triggerTemplate> </rules-core:triggerTemplates><rules-core:actionTemplates xmlns:rules-core=“rules-core”xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”xsi:schemaLocation=“rules-core../../../../rules-core/src/main/resources/rules- core.xsd”><rules-core:actionTemplate id=“137”description=“{STR.RULES.TEMPLATES.ACTION.DESC.RACHIO.OFF}”cvActionId=“137” cvType=“workflow”> <rules-core:inputs><rules-core:input hidden=“false” description=“Which Rachio Object”name=“instanceIds” cvKey=“cloudObjectID” cvType=“cloudObjectID”cvRequired=“true” /> <rules-core:input name=“mediaType”value=“sprinkler/scheduleStop” /> </rules-core:inputs></rules-core:actionTemplate> </rules-core:actionTemplates>Sample curl commands of Rachio cloud rule follows.

curl -k -v -L -H “Content-Type:application/json” -H “X-login:insight” -H“X-password:test” -H “X-AppKey: defaultKey” -X PUT“https://10.0.12.102/rest/icontrol/sites/420/rules” -d ‘{“description”:“Rachio turns ON, Turn onLight”,“executionSource”:“client”,“enabled”:true,“valid”:true,“default”:false,“conditionals”:{“conditional”:[{“triggers”:{“trigger”:[{“description”:“Rachio is ON”,“id”:“0”,“templateId”:“203”,“targetValues”:“1”,“type”:“event”,“mediaTypes”:“sprinkler/systemOn”,“instances”:“181002.0”,“targetComparisonTypes”:“eq”}]},“actions”:{“action”:[{“id”:“0”,“templateId”:“70”,“inputs”:“level=0&”,“instanceIds”:“13000d6f00020a5d9a.1.0”}]}}]}}’User should pass targetComparisonTypes whenever there is a patternpresent in cloudTrigger. In above case targetComparisonTypes is “eq” andtargetValues is “1”. Both these values should be fetched from thetriggerTemplate.Sample curl commands of AccuWeather cloud rule follows.

curl -k -v -L -H “Content-Type:application/json” -H “X-login:insight” -H“X-password:test” -H “X-AppKey: defaultKey” -X PUT“https://10.0.12.102/rest/icontrol/sites/420/rules” -d ‘{“description”:“Outside temperature is less than 100, Turn onlight”,“executionSource”:“client”,“enabled”:true,“valid”:true,“default”:false,“conditionals”:{“conditional”:[{“triggers”:{“trigger”:[{“description”:“Outside temperature is greater than 60degrees, turn on light”,“id”:“0”,“templateId”:“200”,“targetValues”:“70”,“type”:“event”,“mediaTypes”:“weather/temperature”,“instances”:“181001.0”,“targetComparisonTypes”:“gt”}]},“actions”:{“action”:[{“id”:“0”,“templateId”:“70”,“inputs”:“level=0&”,“instanceIds”:“13000d6f00020a5d9a.1.0”}]}}]}}’In above case targetComparisonTypes is “gt” and targetValues is “70”.Here targetComparisonTypes should be fetched from triggerTemplate anduser should pass user defined value in targetValues.SMAP Protocol Changes

SMAP is updated to allow server to send external events to CPE and CPEsend external action event to server.

 <xsd:complexType name=“cloudEvent”>   <xsd:complexContent>   <xsd:extension base=“smap:baseMessage”>     <xsd:sequence>     <xsd:element name=“metaData” type=“smap:eventMetaData”maxOccurs=“32” minOccurs=“0”>       <xsd:annotation>       <xsd:documentation>Additional information about the eventitself</xsd:documentation>       </xsd:annotation>      </xsd:element>     <xsd:element name=“context” type=“smap:eventContext” maxOccurs=“32”minOccurs=“0”>       <xsd:annotation>       <xsd:documentation>Information about other aspects of the systemat the time of the event</xsd:documentation>       </xsd:annotation>     </xsd:element>     </xsd:sequence>     <xsd:attribute name=“id”type=“xsd:token”/>     <xsd:attribute name=“cloudObjectId”type=“xsd:token”/>     <xsd:attribute name=“mediaType” type=“xsd:token”use=“required”/>     <xsd:attribute name=“ts” type=“xsd:long”use=“required”/>     <xsd:attribute name=“href” type=“xsd:anyURI”/>    <xsd:attribute name=“errorCode” type=“xsd:token”/>    <xsd:attribute name=“value” type=“xsd:string”/>    </xsd:extension>  </xsd:complexContent>  </xsd:complexType>  <xsd:complexTypename=“eventContext”>   <xsd:attribute name=“mediaType” type=“xsd:token”use=“required”/>   <xsd:attribute name=“value” type=“xsd:string”use=“required”/>   <xsd:attribute name=“href” type=“xsd:anyURI”/> </xsd:complexType>  <xsd:complexType name=“eventMetaData”>  <xsd:attribute name=“name” type=“xsd:token” use=“required”/>  <xsd:attribute name=“value” type=“xsd:string” use=“required”/> </xsd:complexType>  <xsd:complexType name=“cloudActionEvent”>  <xsd:complexContent>    <xsd:extension base=“smap:baseMessage”>    <xsd:sequence>      <xsd:element name=“ruleId” type=“xsd:long”minOccurs=“0” maxOccurs=“1”>       <xsd:annotation>       <xsd:documentation>Id of the rule that triggered this action, ifapplicable.</xsd:documentation>       </xsd:annotation>     </xsd:element>      <xsd:element name=“eventId” type=“xsd:string”minOccurs=“0” maxOccurs=“1”>       <xsd:annotation>       <xsd:documentation>The id of the event that triggered therule.</xsd:documentation>       </xsd:annotation>      </xsd:element>     <xsd:element name=“cloudObjectId” type=“xsd:token” minOccurs=“1”maxOccurs=“1”/>      <xsd:element name=“actionMediaType”type=“xsd:token” minOccurs=“1” maxOccurs=“1”/>      <xsd:elementname=“actionHref” type=“xsd:anyURI” minOccurs=“0” maxOccurs=“1”/>     <xsd:element name=“actionInput” type=“smap:input” minOccurs=“0”maxOccurs=“32”/>     </xsd:sequence>    </xsd:extension>  </xsd:complexContent>  </xsd:complexType>  <xsd:complexTypename=“input”>   <xsd:attribute name=“name” type=“xsd:token”use=“required”/>   <xsd:attribute name=“mediaType” type=“xsd:token”use=“optional”/>   <xsd:attribute name=“value” type=“xsd:string”use=“required”/>  </xsd:complexType>

The ICS of an embodiment effects ICS platform integration with thirdparty system and device functionality (e.g., Philips Hue lights,Chamberlain garage door openers, Nest thermostats, Dropcam cameras,Doorbot doorbell cameras, etc.), as described in detail herein. Usingthe same processes, other server-to-server (cloud) services (e.g.,Accuweather, MSO digital assets such as voicemail, etc.) are alsointegrated into the ICS platform. FIG. 5 is an example rules interface12 for controlling triggers and actions involving third party devicesintegrated in the CAT, under an embodiment. FIG. 6 is another example ofan actions portion of a rules interface 14 for integrated third partydevices, under an embodiment. FIG. 7 is an example of a triggers portionof a rules interface for third party services integrated with the CAT,under an embodiment. The rules automation actions and triggers of anembodiment include monitor/control functionality enabled via proprietaryUIs, and with cards in the Card UI 13 as described herein.

Cloud Action Triggers (CAT)

Cloud Actions and Triggers (CAT) of an embodiment enable cloud servicesand internet-connected devices to leverage the user interface, RulesEngine and other functions of the service provider system. This allowsthird party devices (e.g., smart door bells, door locks, garage dooroperators, cameras, thermostats, lighting systems, lighting devices,lawn irrigation systems, plant sensors, pet feeders weather stations,rain sensors, pool controls, air quality sensors, music systems, remotecontrollers, internet user interfaces, connected systems, connectedvehicles, etc.), third party services (e.g., weather forecastingservices and applications, family networking services and applications,etc.), and others to trigger automations in the service provider systemusing the Rules Engine. This enables end-users to integrate and usetheir previously-standalone internet connected devices with theirservice provider-based service.

The app icons for security and devices that have states are configuredto provide at-a-glance status to homeowners.

FIG. 8 is an example touchscreen display 18 including numerous Onstates, under an embodiment. The touchscreen On states include, forexample, but are not limited to at least one door unlocked, at least onelight on, and thermostat on, cooling mode, current temperature (73degrees).

FIG. 9 is an example touchscreen display 20 during arming, under anembodiment.

FIG. 10 is an example touchscreen display 22 including numerous Offstates, under an embodiment. The touchscreen Off states include, forexample, but are not limited to at least one all doors locked, alllights off, and thermostat off.

Embodiments include event-based CAT Rules comprising a Card UIconfigured to perform operations including but not limited to creating,editing and deleting a rule via the REST API, focusing exclusively ontrigger events that lead to actions (e.g., weather trigger events(Accuweather) to invoke actions, irrigation system trigger events(Rachio) to invoke actions, etc.).

As an example, the triggers of an embodiment used to drive use caserequirements for a weather service integration include but are notlimited to current temperature (Celsius, Fahrenheit), currentprecipitation conditions (Rain yes/no, Snow yes/no), daily temperatureforecast high (Celsius, Fahrenheit), daily temperature forecast low(Celsius, Fahrenheit), daily forecast for precipitations (Rain yes/no,Snow yes/no), severe weather alert (Yes/No). Example use cases of theAccuweather configuration include, but are not limited to forecastindicator (e.g., mornings between 6 am and 7 am, turn on/off light, orchange light color to reflect daily weather forecast), outdoortemperature controls a Relays+ device, such as a fan or pet door, turnon a vacation home thermostat only within a certain outdoor temperaturerange, get text messages when temperature reaches over/below a certainthreshold, and receive severe weather alerts over text messages.

FIGS. 11-30 are example implementations of the CAT rules andcorresponding device displays involving the AccuWeather deviceapplication (app), under an embodiment. These example screens, whichinclude mnemonic icons and state summaries to represent the rule names,differ from conventional displays presenting a list of lengthysentences, thereby retaining the simplicity of IFTT, but with greaterdetail to differentiate between rules.

FIG. 11 is an example touchscreen display 19 of a rules list, under anembodiment.

FIG. 12 is an example touchscreen display 21 in response to selection ofthe “Add Rule” icon, under an embodiment.

FIG. 13 is an example touchscreen displayed 23 upon selection of the“Weather Event” icon, including a list of weather events, under anembodiment.

FIG. 14 is an example touchscreen 24 displayed upon selection of the“Reports a temperature” icon, including selections for activating lowand high temperature selections, under an embodiment. This display cansupport TEMP is ABOVE or BELOW settings, rather than range, but is notso limited.

FIG. 15 is an example touchscreen display 25 for selecting a temperaturelimit (lower) for “Reports a temperature” (“choose low”), under anembodiment.

FIG. 16 is an example touchscreen display 26 following selection of atemperature limit (lower) for “Reports a temperature”, under anembodiment.

FIG. 17 is an example touchscreen display 27 for selecting a temperaturelimit (upper) for “Reports a temperature”, under an embodiment.

FIG. 18 is an example touchscreen display 28 following selection of atemperature limit (upper) for “Reports a temperature”, under anembodiment.

FIG. 19 is an example touchscreen display 29 for filtering thetemperature reporting rule based on time or day, under an embodiment.

FIG. 20 is an example touchscreen display 30 for selecting a time afterselecting “any day” as a filtering parameter for the temperaturereporting rule, under an embodiment.

FIG. 21 is an example touchscreen display 31 for selecting system stateas an event filter for the temperature reporting rule, under anembodiment.

FIG. 22 is an example touchscreen display 32 for which two arming typesare selected for system state as an event filter for the temperaturereporting rule, under an embodiment.

FIG. 23 is an example touchscreen display 33 presenting availableactions for the temperature reporting rule, under an embodiment.

FIG. 24 is an example touchscreen display 34 for selecting a type ofdevice to control in response to choosing an action to control a deviceaccording to a temperature reporting rule, under an embodiment.

FIG. 25 is an example touchscreen display 35 for displaying a list ofdevice types corresponding to the selected device type to be controlledunder the temperature reporting rule, under an embodiment.

FIG. 26 is an example touchscreen display 36 showing selection of aparticular ceiling fan device (“Patio”) under the temperature reportingrule, under an embodiment.

FIG. 27 is an example touchscreen display 37 showing available actionsof the selected device for control under the temperature reporting rule,under an embodiment.

FIG. 28 is an example touchscreen display 38 showing options forcreating a compound rule with additional actions, under an embodiment.

FIG. 29 is an example touchscreen display 39 for saving a rule, under anembodiment.

FIG. 30 is an example touchscreen display 40 of a rules list followingcreation of a new rule, under an embodiment.

FIG. 31 is an example touchscreen display 41 of a rules list, under anembodiment.

FIG. 32 is an example touchscreen display 42 in response to selection ofthe “Add Rule” icon, under an embodiment.

FIG. 33 is an example touchscreen 43 displayed upon selection of the“Irrigation” icon, including a list of irrigation events, under anembodiment.

FIG. 34 is an example touchscreen 44 displayed upon selection of the“Switches on” icon, including selections for a day for the switchingevent, under an embodiment.

FIG. 35 is an example touchscreen display 45 for selecting an “on” timeafter selecting “any day” as a filtering parameter for the switchingevent, under an embodiment.

FIG. 36 is an example touchscreen display 46 for selecting a time of dayas a start time, under an embodiment.

FIG. 37 is an example touchscreen display 47 following selection of astart time for the switching event rule, under an embodiment.

FIG. 38 is an example touchscreen display 48 for selecting a time of dayas an end time, under an embodiment.

FIG. 39 is an example touchscreen display 49 following selection of astart time and an end time for the switching event rule, under anembodiment.

FIG. 40 is an example touchscreen display 50 for selecting system stateas an event filter for the switching event rule, under an embodiment.

FIG. 41 is an example touchscreen display 51 presenting availableactions for the switching event rule, under an embodiment.

FIG. 42 is an example touchscreen display 52 for selecting a type ofdevice to control in response to choosing an action for the switchingevent rule, under an embodiment.

FIG. 43 is an example touchscreen display 53 for displaying a list ofdevice types corresponding to the selected device type (“lights”) to becontrolled under the switching event rule, under an embodiment.

FIG. 44 is an example touchscreen display 54 showing selection ofparticular lighting devices (“Porch” and “Living Room”) under theswitching event rule, under an embodiment.

FIG. 45 is an example touchscreen display 55 showing available actionsof the selected device (“Porch light”) for control under the switchingevent rule, under an embodiment.

FIG. 46 is an example touchscreen display 56 showing available actionsof another selected device (“Living Room light”) for control under theswitching event rule, under an embodiment.

FIG. 47 is an example touchscreen display 57 showing options forcreating a compound rule with additional actions under the switchingevent rule, under an embodiment.

FIG. 48 is an example touchscreen display 58 for selecting a type ofdevice to control in response to choosing an additional control devicefor a compound switching event rule, under an embodiment.

FIG. 49 is an example touchscreen display 59 for displaying a list ofdevice types corresponding to the selected device type (“shades”) to becontrolled under the compound switching event rule, under an embodiment.

FIG. 50 is an example touchscreen display 60 showing available actionsof the selected device (“Living room shades”) for control under thecompound switching event rule, under an embodiment.

FIG. 51 is an example touchscreen display 61 for saving a rule, under anembodiment.

FIG. 52 is an example touchscreen display 62 of a rules list followingcreation of the new switching event rule, under an embodiment.

Card UI

The ICS of an embodiment includes a Card UI, as described in detailherein. The Card UI of an embodiment provides a clean, simple and easilynavigable interface with UI elements grouped into a card-likeconfiguration. This framework can then be customized by MSOs andaugmented by third-party vendors with their own cards. The Card UIincludes a software development kit (SDK) that enables third-partydevelopers to integrate additional features into the applicationinfrastructure. The third-party cards integrate into the existing CardUI framework, thus allowing developers to generate and add newfunctionality into one or more of the smartphone, tablet and subscriberportal. The SDK also provides a sandbox for the service providers IP,and the cards run in the sandbox to protect that apps and users, and notexpose the developer to critical IP elements of the application (e.g.,source code, etc.).

FIG. 53 is a flow diagram 63 for local card development and unittesting, under an embodiment. FIG. 54 is a flow diagram 64 for cardintegration testing, under an embodiment. FIG. 55 is a flow diagram 65for card production, under an embodiment. FIG. 56 is an example card 66(e.g., thermostat, etc.) operating on a smart phone, under anembodiment. FIG. 57 is an example small card 67 (e.g., thermostat,etc.), under an embodiment. FIG. 58 is an example card menu 68, under anembodiment.

In a desktop browser, the sandbox is an iframe so that the “sandboxed”attribute on the iframe provides for extra isolation, which isimplemented on all supported browsers. The main app provides a limitedAPI to the sandbox via the PostMessage function, and the cards of anembodiment are served from a different origin than the main app toprevent unrestricted access to the service provider server via sharedcookies.

Regarding cards operating on a smartphone, each multiple-system operator(MSO) has limited control over the positioning and sizing of the thirdparty cards. On a smartphone, the card is displayed full screen, exceptfor a header provided and branded by the core app in the main webView.Native code sizes the card webview and layers it over the app's mainwebview. Tablet builds include an option to show “small mode” cards in apopup. A mini card on a view acts like a button that will trigger thepopup. Alternatively if the card prefers “large mode”, it can occupy thewhole tablet screen (except the header).

The cards of an embodiment will not control their size, so they managethe various different sizes used by the wide range of mobile devices,but the embodiment is not so limited. An embodiment includes differentsize modes, for example, a small mode (e.g., the size of a card or aphone screen, and a large mode (e.g., the full size of a tablet screenor full content window). All cards support small mode as this is theonly mode on a phone. As part of their packaging the developer canindicate whether they prefer large mode. See below for some examples ofhow these will appear.

When displayed or presented in a smartphone, the cards of an embodimentappear “full screen” (apart from a header above it), and appear “fullscreen” on a tablet device and/or a browser if the card is configured toprefer large mode. The cards of an embodiment are displayed in a popupformat on a tablet device if the cards are configured to not prefer thelarge mode.

The cards are alternatively displayed via a browser as mixed in withother cards in a single view if the cards are configured so as to notprefer the large mode. As an alternative to a full screen display, thecards may be displayed as mixed in with other cards in a single view onsmartphones, and used instead of popups on tablet devices, but theembodiment is not so limited.

The Card UI Manage Views code is extended to enable users to addthird-party cards to views. The Card packaging indicates to the Card UIwhat type of device it controls (if any), and whether it controls one ormore of those devices. When controlling a single device, Card UI ManageViews code stores that association and informs the Card as to whichdevice ID it is associated when it starts.

The SDK of an embodiment includes or exposes APIs (e.g., javascript)that enable the developer to interact with the service provider devicesat the premises. One such API, for example, is as follows:

getDevices ({lights: true}); // --> [“1234”, “5678”]; list of deviceIdsfor lights getDeviceState (“1234”); // {type: “light”, on: true,dimLevel: 50} setDeviceState (“1234”, {on: true}); // switch a light on// Register for light and thermostat state updates // Command failuresor device troubles will also be sent to this function registerForUpdates({lights: true, thermostats: true}, myStateUpdateFunction); ! //register for state updates for 2 devices registerForUpdates ({deviceIds:[“1234”, “5678”]}, myStateUpdateFunction);

Additional API examples of an embodiment include but are not limited tothe following:

-   -   a. App lifetime: Events deviceready, pause, resume; informs card        about app status; deviceready is simulated by the Card UI for        browsers.    -   b. Card lifetime: Activate, deactivate; activate has a parameter        for the device ID if the card is dealing with a single home        device.    -   c. Preference storage: enables card developers to store user        preferences or external server credentials; stored in the same        location as for the rest of the app (e.g., keychain for IOS,        encrypted file for Android, obfuscated localStore for browser,        etc.).    -   d. Device APIs: For mobile devices, access to APIs including        Device (hardware model, OS, unique app specific device ID),        Network-information (offline/cellular/Wi-Fi), Globalization        (locale+date/currency display functions).    -   e. Title update: Card uses this to update title bar        appropriately for this card.

The SDK of an embodiment enables developer access to the browser DOMAPIs so that numerous frameworks are available (e.g. jquery, backbone,etc). The SDK enables developers to manage their own access to externalservers direct from their card's code, and to have full access via XHR,controlled by a whitelist on mobile apps.

External server APIs needing authentication are routed through thepartner proxy API. Developers first register for OAuth onboarding withthe service provider and, once onboarded and the OAuth processcompleted, the partner proxy API is available to the card. This APIautomatically appends an access token to the request, makes the call tothe external server, and returns the raw response. An example of thispartner proxy API is as follows:

cardsdk.partnerProxyCall(path, callback, method, parameters) path: theendpoint of the external API, given either as an absolute or relativeURL callback: function(success, data){ }   success: returns true if therequest completed successfully, else false   data: a JSON objectcontaining either the response wrapped in a response object (on success)or detail of the error on failure.   method: (optional) one of GET, PUT,POST, DELETE. Defaults to   GET.   parameters: (optional) a URL encodedstring of any parameters to   include.

Makes an authenticated call to the external server specified.

For example:

cardsdk.partnerProxyCall(“/1/public/device/dc345cf5-a6f7-4654-b8ce-4161d0445593/event”, apiCallCallback, “GET”,“startTime%3D1414818000000%26endTime%3D1415739608103”) functionapiCallCallback(success, data) {   if(success) // Success of the partnerproxy API call   {     var myRes = data.response;    if(myRes.statusCode == 200) // Success of my external server APIcall       var someData = myRes.content; // Body of the external server      response   } } A data object on success: {   “response”:   {    “headers”: [       {“Date”:[“Thu, 13 Nov 2014 23:22:11 GMT”]},      {“Content-Length”:[“50”]},       {“Connection”:[“keep-alive”]},      {“Content-Type”:[“application\/json”]},      {“Server”:[“Apache-Coyote\/1.1”]}     ],    “content”; “{\“current\”:\“0b881a86-6262-4c00-8d44-5f0b1f324c7e\”}”,    “statusCode”: 200,     “contentType”: “application\/json”,    “contentEncoding”: “UTF-8”   } } And on failure: {“error”: “Someerror message”}

The app of an embodiment controls the lifetime of cards and, as such,creates a card when it needs to be displayed, and destroys a card at anytime when it is not displayed (e.g., depending on how many cards are inuse and any memory pressure). When a user wishes to view a card again,the app re-creates the card transparently, and in time for any slidetransition to display smoothly.

A card indicates in its packaging whether it needs to be runningconstantly when the app runs (e.g., long-lived third party serverconnection, need to be alerted to device status changes immediately uponoccurrence, etc.). The app handles status updates from the server andupdates its own internal memory model with the new status, which itshares with cards when needed. Whenever a card is started or restarted,the app feeds it the latest state of its associated device or devices,so there is generally no need for a card to be running continuously.

An embodiment includes a stub environment for testing and debugging acard. The stub environment enables developers to build, test and debugtheir cards in a self-contained environment, without access to serviceprovider app source code and, as such, does not require a serviceprovider server or account. Instead, the APIs described herein aresimulated using local javascript only, making it trivial to simulate newfeatures in the stub environment without waiting for those features toappear in the service provider apps or server.

For mobile apps, the stub environment is based around Cordova (AKAPhonegap). Developers use the base SDK javascript files, mix in theircard files, and build, package and sign their own mobile apps fortesting using Cordova and IOS/Android tools, but the embodiment is notso limited. The app includes one or more dummy cards, and thedeveloper's own card or cards so that developers can test card behavioron a wide range of mobile devices. Cards of an embodiment are debuggedusing “Web Inspector” (provided with IOS and Android dev tools) but arenot so limited.

An embodiment provides the stub environment as HTML/JS/CSS files.Developers can include their card files, and run these locally on theirdevelopment machine, or upload to a web server of their choice, anddebugging is via the Web Inspector in their browser. The stubenvironment is configured with a JSON file that specifies the devices ofthe stub system, their initial states, and also allows state changes ortroubles to be simulated after fixed periods of time (e.g., can requesta stub system with 6 lights, 3 thermostats, 2 water sensors, and requesta water sensor trip or trouble 1 minute after startup).

The system of an embodiment includes a Card Portal comprising a web sitethat enables developers to do one or more of create a developer account,download the Card SDK, register a card and its ID (e.g.,com.mycompany.myfirstcard), upload a card (see later for packagingdetails), perform basic automatic validation of the card and package,run a card in the service provider app, and request review andcertification of a card by the service provider.

The Card Portal of an embodiment is written in node.js, but is not solimited. After testing the debugging in the Stub Environment, the cardis then tested inside the service provider app within the serviceprovider system. To do so, the developer installs the service providerbranded app from the app store. In “settings” of the service providerapp, the developer selects a checkbox indicating they are a developerand, in response, the app prompts for the user's developer account andpassword, validates the user at the Card Portal, downloads a list of theuser's Cards, displays the list of cards so that the user checks eachone they want to have loaded at startup, and downloads the cards inbackground.

Once downloaded, the developer is presented a message (e.g., “New cardshave been downloaded. Restart the app to use them”). During a subsequentapp start, it automatically checks for updated cards, downloads them inthe background, and then prompts the user/developer as before torestart. Unlike the stub environment, the developer will not have debugaccess inside the service provider app, but will receive log statements(e.g., route any log statements from their app to the regular devicelogs (xcode/adb/browser console), but the embodiment is not so limited.

Cards of an embodiment are uploaded to the Card Portal as a zip filethat includes the HTML, CSS, JS, and resource files. A card.json file isalso to be included with the cards, which has details of thecorresponding card behavior as described herein. The card.json fileincludes an object with the following properties: id (id of third partycard); integraionld (id for the partner integration with the iControlserver this will enable developers to develop multiple cards with onepartner integration); version (three point version string of the form“<int>.<int>.<int>”); name (display name of card); deviceType (e.g.,other, info, irrigation, doors, thermostats, lights, cameras,dryContact, motion, co, water, etc.); appStateTypes (array of all devicetypes for which a card would like to receive the state); deviceImg(filename of the image to be displayed in the onboarding section of theapp); preferLargeMode (a card is loaded either full screen or inside apopup on tablet and smartphone, this flag enables “always full screen”if true); startFile (filename of the HTML file to load on card startup);runInBackground (if true, the app will try to keep the card in memoryafter a user navigates away from it, but card may be destroyed at anytime).

Once the developer has tested their card in the service provider app,they use the Card Portal to request card certification by the serviceprovider. Considerations for certification include that the cardperforms reliably and satisfactorily, does not damage performance or UXof the service provider app when integrated, use of external servers isappropriate, and card works correctly across range of phones, tabletsand browsers. A version of a card is initially certified by the serviceprovider, and newly updated versions may undergo further review.Alternatively, trusted developers might be allowed to provide updates totheir already certified cards without any further review.

The app build system is extended to pull certain certified cards fromthe Card Portal and include them in the MSO app and smartphone builds.Each MSO can have its own choice of cards, card versions and cardlanguages, but the embodiment is not so limited. Alternatively, the CardPortal may be extended to distribute cards dynamically to real users,instead of baking the cards into an app.

Branding and internationalization of cards is enabled for third partydevelopers wishing to project their own brand on their card, or useexisting HTML5 code in their card. Furthermore, MSOs wishing to buildtheir own cards have access to select JS and CSS files as part of theSDK that implement basic widgets, spinners and styles used throughoutthe mobile apps.

Card developers are able to extend their card IDs to identify particularvariants that the app build system can pick up, for example:

// Developer registers this card ID: com.superlights.multicolor Exampleindividual MSO and/or language variantscom.superlights.multicolor.comcast com.superlights.multicolor.rogers.frcom.superlights.multicolor.rogers.en corn.superlights.multicolor.fr

The card packaging parameters of an embodiment (in card.json) includeCard ID (e.g., com.mycompany.myfirstcard), Card Version (e.g., 1.2.15),Server Whitelist (e.g., https://myserver.com,https://myotherserver.com), Prefers large mode (If true, card prefers“full screen” on tablet and smartphone, Runs all the time (If true, appshould not kill card to save resources), Name of startup file (e.g.,index.html), Device types (e.g., “lights”, “thermostats”), and Singledevice (If true, card controls a single device).

Once certified, cards are onboarded by the service provider. Thedescription of the onboarding process that follows is presented in thecontext of an example in which partner devices (partners) include athird party service (e.g., accuWeather), a thermostat (e.g., Nest), anda sprinkler control system (e.g., Rachio), but the embodiment is not solimited.

A list of available (within ICS) cloud partners is generated using thepartnerNames API of the Card SDK to retrieve a comma-delimited list ofpartners.

https://qacluster-converge.icontrol.com/rest/icontrol/sites/291/partnerNames  Expand source // returns this  accuWeather,nest,rachio

An embodiment calls the cloudObjectByProvider API to get details orinstances for a cloud partner. If this API returns a list of deviceinstances, then the partner has already been on-boarded.

A token is then generated to pass to the OAuth onboarding API, as asecurity measure, but the embodiment is not so limited.

https://qacluster- converge.icontrol.com/rest/icontrol/sites/291/generateTokenForCloudObjectOnboarding? providerName=nest  Expand source// 200: returns this  <some_token>  // 409: return thisThe account is not provisioned for the operation.

The OAuth login configuration is persisted in the database, therebyeliminating any need to pass it down to the mobile app or cards. TheoauthRedirect API is used to onboard, and the server sends theappropriate requests to start the on boarding process.

https://qacluster-converge.icontrol.com/oauth/oauthRedirect/nest?token=<some_token> // nothing returned here but we wait for aredirect

Within the app, the request is redirected to/cui/onboardingcompleted.html, which calls postMessage to inform the appknow the onboarding was completed (seen below).

Expand source <!-- Onboarding Complete -->  <html>  <head>  <scripttype=“text/javascript”>  var queryParams =location.search.slice(1).split(‘&’).map(function(a) { returna.split(‘=’);});  var partnerId = (queryParams.filter(function(a){return a[0] == “partner” })[0] || [ ])[1] ||“”;  var accountId =(queryParams.filter(function(a){ return a[0] == “accountId” })[0] || [])[1]|| “”;  window.opener && window.opener.postMessage(partnerId+“_onboardingcomplete”, “*”); // We should be in a popup window, so sendthe parent window a message  </script>  </head>  <body></body>  </html>   Once the “nest_onboardingcomplete” postMessage is called (e.g., Nestthermostat), the app can then display the card.Integrated Security System

The ICS of an embodiment includes one or more components of an“integrated security system” as described in detail herein. An exampleof the “integrated security system” is available as one or more of thenumerous systems or platforms available from iControl Networks, Inc.,Redwood City, Calif. The ICS of an embodiment is coupled to,incorporates, and/or integrates with one or more components of the“integrated security system”.

As but one example, an integrated security system is described hereinthat integrates broadband and mobile access and control withconventional security systems and premise devices to provide a tri-modesecurity network (broadband, cellular/GSM, POTS access) that enablesusers to remotely stay connected to their premises. The integratedsecurity system, while delivering remote premise monitoring and controlfunctionality to conventional monitored premise protection, complementsexisting premise protection equipment. The integrated security systemintegrates into the premise network and couples wirelessly with theconventional security panel, enabling broadband access to premisesecurity systems. Automation devices (cameras, lamp modules,thermostats, etc.) can be added, enabling users to remotely see livevideo and/or pictures and control home devices via their personal webportal or webpage, mobile phone, and/or other remote client device.Users can also receive notifications via email or text message whenhappenings occur, or do not occur, in their home.

In accordance with the embodiments described herein, a wireless system(e.g., radio frequency (RF)) is provided that enables a securityprovider or consumer to extend the capabilities of an existingRF-capable security system or a non-RF-capable security system that hasbeen upgraded to support RF capabilities. The system includes anRF-capable Gateway device (physically located within RF range of theRF-capable security system) and associated software operating on theGateway device. The system also includes a web server, applicationserver, and remote database providing a persistent store for informationrelated to the system.

The security systems of an embodiment, referred to herein as theiControl security system or integrated security system, extend the valueof traditional home security by adding broadband access and theadvantages of remote home monitoring and home control through theformation of a security network including components of the integratedsecurity system integrated with a conventional premise security systemand a premise local area network (LAN). With the integrated securitysystem, conventional home security sensors, cameras, touchscreenkeypads, lighting controls, and/or Internet Protocol (IP) devices in thehome (or business) become connected devices that are accessible anywherein the world from a web browser, mobile phone or through content-enabledtouchscreens. The integrated security system experience allows securityoperators to both extend the value proposition of their monitoredsecurity systems and reach new consumers that include broadband usersinterested in staying connected to their family, home and property whenthey are away from home.

The integrated security system of an embodiment includes securityservers (also referred to herein as iConnect servers or security networkservers) and an iHub gateway (also referred to herein as the gateway,the iHub, or the iHub client) that couples or integrates into a homenetwork (e.g., LAN) and communicates directly with the home securitypanel, in both wired and wireless installations. The security system ofan embodiment automatically discovers the security system components(e.g., sensors, etc.) belonging to the security system and connected toa control panel of the security system and provides consumers with fulltwo-way access via web and mobile portals. The gateway supports variouswireless protocols and can interconnect with a wide range of controlpanels offered by security system providers. Service providers and userscan then extend the system's capabilities with the additional IPcameras, lighting modules or security devices such as interactivetouchscreen keypads. The integrated security system adds an enhancedvalue to these security systems by enabling consumers to stay connectedthrough email and SMS alerts, photo push, event-based video capture andrule-based monitoring and notifications. This solution extends the reachof home security to households with broadband access.

The integrated security system builds upon the foundation afforded bytraditional security systems by layering broadband and mobile access, IPcameras, interactive touchscreens, and an open approach to homeautomation on top of traditional security system configurations. Theintegrated security system is easily installed and managed by thesecurity operator, and simplifies the traditional security installationprocess, as described below.

The integrated security system provides an open systems solution to thehome security market. As such, the foundation of the integrated securitysystem customer premises equipment (CPE) approach has been to abstractdevices, and allows applications to manipulate and manage multipledevices from any vendor. The integrated security system DeviceConnecttechnology that enables this capability supports protocols, devices, andpanels from GE Security and Honeywell, as well as consumer devices usingZ-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IPtouchscreens. The DeviceConnect is a device abstraction layer thatenables any device or protocol layer to interoperate with integratedsecurity system components. This architecture enables the addition ofnew devices supporting any of these interfaces, as well as add entirelynew protocols.

The benefit of DeviceConnect is that it provides supplier flexibility.The same consistent touchscreen, web, and mobile user experience operateunchanged on whatever security equipment selected by a security systemprovider, with the system provider's choice of IP cameras, backend datacenter and central station software.

The integrated security system provides a complete system thatintegrates or layers on top of a conventional host security systemavailable from a security system provider. The security system providertherefore can select different components or configurations to offer(e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modifythe integrated security system configuration for the system provider'sspecific needs (e.g., change the functionality of the web or mobileportal, add a GE or Honeywell-compatible TouchScreen, etc.).

The integrated security system integrates with the security systemprovider infrastructure for central station reporting directly viaBroadband and GPRS alarm transmissions. Traditional dial-up reporting issupported via the standard panel connectivity. Additionally, theintegrated security system provides interfaces for advancedfunctionality to the CMS, including enhanced alarm events, systeminstallation optimizations, system test verification, videoverification, 2-way voice over IP and GSM.

The integrated security system is an IP centric system that includesbroadband connectivity so that the gateway augments the existingsecurity system with broadband and GPRS connectivity. If broadband isdown or unavailable GPRS may be used, for example. The integratedsecurity system supports GPRS connectivity using an optional wirelesspackage that includes a GPRS modem in the gateway. The integratedsecurity system treats the GPRS connection as a higher cost thoughflexible option for data transfers. In an embodiment the GPRS connectionis only used to route alarm events (e.g., for cost), however the gatewaycan be configured (e.g., through the iConnect server interface) to actas a primary channel and pass any or all events over GPRS. Consequently,the integrated security system does not interfere with the current plainold telephone service (POTS) security panel interface. Alarm events canstill be routed through POTS; however the gateway also allows suchevents to be routed through a broadband or GPRS connection as well. Theintegrated security system provides a web application interface to theCSR tool suite as well as XML web services interfaces for programmaticintegration between the security system provider's existing call centerproducts. The integrated security system includes, for example, APIsthat allow the security system provider to integrate components of theintegrated security system into a custom call center interface. The APIsinclude XML web service APIs for integration of existing security systemprovider call center applications with the integrated security systemservice. All functionality available in the CSR Web application isprovided with these API sets. The Java and XML-based APIs of theintegrated security system support provisioning, billing, systemadministration, CSR, central station, portal user interfaces, andcontent management functions, to name a few. The integrated securitysystem can provide a customized interface to the security systemprovider's billing system, or alternatively can provide security systemdevelopers with APIs and support in the integration effort.

The integrated security system provides or includes business componentinterfaces for provisioning, administration, and customer care to name afew. Standard templates and examples are provided with a definedcustomer professional services engagement to help integrate OSS/BSSsystems of a Service Provider with the integrated security system.

The integrated security system components support and allow for theintegration of customer account creation and deletion with a securitysystem. The iConnect APIs provides access to the provisioning andaccount management system in iConnect and provide full support foraccount creation, provisioning, and deletion. Depending on therequirements of the security system provider, the iConnect APIs can beused to completely customize any aspect of the integrated securitysystem backend operational system.

The integrated security system includes a gateway that supports thefollowing standards-based interfaces, to name a few: Ethernet IPcommunications via Ethernet ports on the gateway, and standardXML/TCP/IP protocols and ports are employed over secured SSL sessions;USB 2.0 via ports on the gateway; 802.11b/g/n IP communications;GSM/GPRS RF WAN communications; CDMA 1×RTT RF WAN communications(optional, can also support EVDO and 3G technologies).

The gateway supports the following proprietary interfaces, to name afew: interfaces including Dialog RF network (319.5 MHz) and RS485Superbus 2000 wired interface; RF mesh network (908 MHz); and interfacesincluding RF network (345 MHz) and RS485/RS232bus wired interfaces.

Regarding security for the IP communications (e.g., authentication,authorization, encryption, anti-spoofing, etc), the integrated securitysystem uses SSL to encrypt all IP traffic, using server andclient-certificates for authentication, as well as authentication in thedata sent over the SSL-encrypted channel. For encryption, integratedsecurity system issues public/private key pairs at the time/place ofmanufacture, and certificates are not stored in any online storage in anembodiment.

The integrated security system does not need any special rules at thecustomer premise and/or at the security system provider central stationbecause the integrated security system makes outgoing connections usingTCP over the standard HTTP and HTTPS ports. Provided outbound TCPconnections are allowed then no special requirements on the firewallsare necessary.

FIG. 59 is a block diagram of the integrated security system 100, underan embodiment. The integrated security system 100 of an embodimentincludes the gateway 102 and the security servers 104 coupled to theconventional home security system 110. At a customer's home or business,the gateway 102 connects and manages the diverse variety of homesecurity and self-monitoring devices. The gateway 102 communicates withthe iConnect Servers 104 located in the service provider's data center106 (or hosted in integrated security system data center), with thecommunication taking place via a communication network 108 or othernetwork (e.g., cellular network, internet, etc.). These servers 104manage the system integrations necessary to deliver the integratedsystem service described herein. The combination of the gateway 102 andthe iConnect servers 104 enable a wide variety of remote client devices120 (e.g., PCs, mobile phones and PDAs) allowing users to remotely stayin touch with their home, business and family. In addition, thetechnology allows home security and self-monitoring information, as wellas relevant third party content such as traffic and weather, to bepresented in intuitive ways within the home, such as on advancedtouchscreen keypads.

The integrated security system service (also referred to as iControlservice) can be managed by a service provider via browser-basedMaintenance and Service Management applications that are provided withthe iConnect Servers. Or, if desired, the service can be more tightlyintegrated with existing OSS/BSS and service delivery systems via theiConnect web services-based XML APIs.

The integrated security system service can also coordinate the sendingof alarms to the home security Central Monitoring Station (CMS) 199.Alarms are passed to the CMS 199 using standard protocols such asContact ID or SIA and can be generated from the home security panellocation as well as by iConnect server 104 conditions (such as lack ofcommunications with the integrated security system). In addition, thelink between the security servers 104 and CMS 199 provides tighterintegration between home security and self-monitoring devices and thegateway 102. Such integration enables advanced security capabilitiessuch as the ability for CMS personnel to view photos taken at the time aburglary alarm was triggered. For maximum security, the gateway 102 andiConnect servers 104 support the use of a mobile network (both GPRS andCDMA options are available) as a backup to the primary broadbandconnection.

The integrated security system service is delivered by hosted serversrunning software components that communicate with a variety of clienttypes while interacting with other systems. FIG. 60 is a block diagramof components of the integrated security system 100, under anembodiment. Following is a more detailed description of the components.

The iConnect servers 104 support a diverse collection of clients 120ranging from mobile devices, to PCs, to in-home security devices, to aservice provider's internal systems. Most clients 120 are used byend-users, but there are also a number of clients 120 that are used tooperate the service.

Clients 120 used by end-users of the integrated security system 100include, but are not limited to, the following:

-   -   Clients based on gateway client applications 202 (e.g., a        processor-based device running the gateway technology that        manages home security and automation devices).    -   A web browser 204 accessing a Web Portal application, performing        end-user configuration and customization of the integrated        security system service as well as monitoring of in-home device        status, viewing photos and video, etc. Device and user        management can also be performed by this portal application.    -   A mobile device 206 (e.g., PDA, mobile phone, etc.) accessing        the integrated security system Mobile Portal. This type of        client 206 is used by end-users to view system status and        perform operations on devices (e.g., turning on a lamp, arming a        security panel, etc.) rather than for system configuration tasks        such as adding a new device or user.    -   PC or browser-based “widget” containers 208 that present        integrated security system service content, as well as other        third-party content, in simple, targeted ways (e.g. a widget        that resides on a PC desktop and shows live video from a single        in-home camera). “Widget” as used herein means applications or        programs in the system.    -   Touchscreen home security keypads 208 and advanced in-home        devices that present a variety of content widgets via an        intuitive touchscreen user interface.    -   Notification recipients 210 (e.g., cell phones that receive        SMS-based notifications when certain events occur (or don't        occur), email clients that receive an email message with similar        information, etc.).    -   Custom-built clients (not shown) that access the iConnect web        services XML API to interact with users' home security and        self-monitoring information in new and unique ways. Such clients        could include new types of mobile devices, or complex        applications where integrated security system content is        integrated into a broader set of application features.

In addition to the end-user clients, the iConnect servers 104 support PCbrowser-based Service Management clients that manage the ongoingoperation of the overall service. These clients run applications thathandle tasks such as provisioning, service monitoring, customer supportand reporting.

There are numerous types of server components of the iConnect servers104 of an embodiment including, but not limited to, the following:Business Components which manage information about all of the homesecurity and self-monitoring devices; End-User Application Componentswhich display that information for users and access the BusinessComponents via published XML APIs; and Service Management ApplicationComponents which enable operators to administer the service (thesecomponents also access the Business Components via the XML APIs, andalso via published SNMP MIBs).

The server components provide access to, and management of, the objectsassociated with an integrated security system installation. Thetop-level object is the “network.” It is a location where a gateway 102is located, and is also commonly referred to as a site or premises; thepremises can include any type of structure (e.g., home, office,warehouse, etc.) at which a gateway 102 is located. Users can onlyaccess the networks to which they have been granted permission. Within anetwork, every object monitored by the gateway 102 is called a device.Devices include the sensors, cameras, home security panels andautomation devices, as well as the controller or processor-based devicerunning the gateway applications.

Various types of interactions are possible between the objects in asystem. Automations define actions that occur as a result of a change instate of a device. For example, take a picture with the front entrycamera when the front door sensor changes to “open”. Notifications aremessages sent to users to indicate that something has occurred, such asthe front door going to “open” state, or has not occurred (referred toas an iWatch notification). Schedules define changes in device statesthat are to take place at predefined days and times. For example, setthe security panel to “Armed” mode every weeknight at 11:00 pm.

The iConnect Business Components are responsible for orchestrating allof the low-level service management activities for the integratedsecurity system service. They define all of the users and devicesassociated with a network (site), analyze how the devices interact, andtrigger associated actions (such as sending notifications to users). Allchanges in device states are monitored and logged. The BusinessComponents also manage all interactions with external systems asrequired, including sending alarms and other related self-monitoringdata to the home security Central Monitoring System (CMS) 199. TheBusiness Components are implemented as portable Java J2EE Servlets, butare not so limited.

The following iConnect Business Components manage the main elements ofthe integrated security system service, but the embodiment is notso-limited:

-   -   A Registry Manager 220 defines and manages users and networks.        This component is responsible for the creation, modification and        termination of users and networks. It is also where a user's        access to networks is defined.    -   A Network Manager 222 defines and manages security and        self-monitoring devices that are deployed on a network (site).        This component handles the creation, modification, deletion and        configuration of the devices, as well as the creation of        automations, schedules and notification rules associated with        those devices.    -   A Data Manager 224 manages access to current and logged state        data for an existing network and its devices. This component        specifically does not provide any access to network management        capabilities, such as adding new devices to a network, which are        handled exclusively by the Network Manager 222.    -   To achieve optimal performance for all types of queries, data        for current device states is stored separately from historical        state data (a.k.a. “logs”) in the database. A Log Data Manager        226 performs ongoing transfers of current device state data to        the historical data log tables.

Additional iConnect Business Components handle direct communicationswith certain clients and other systems, for example:

-   -   An iHub Manager 228 directly manages all communications with        gateway clients, including receiving information about device        state changes, changing the configuration of devices, and        pushing new versions of the gateway client to the hardware it is        running on.    -   A Notification Manager 230 is responsible for sending all        notifications to clients via SMS (mobile phone messages), email        (via a relay server like an SMTP email server), etc.    -   An Alarm and CMS Manager 232 sends critical server-generated        alarm events to the home security Central Monitoring Station        (CMS) and manages all other communications of integrated        security system service data to and from the CMS.    -   The Element Management System (EMS) 234 is an iControl Business        Component that manages all activities associated with service        installation, scaling and monitoring, and filters and packages        service operations data for use by service management        applications. The SNMP MIBs published by the EMS can also be        incorporated into any third party monitoring system if desired.

The iConnect Business Components store information about the objectsthat they manage in the iControl Service Database 240 and in theiControl Content Store 242. The iControl Content Store is used to storemedia objects like video, photos and widget content, while the ServiceDatabase stores information about users, networks, and devices. Databaseinteraction is performed via a JDBC interface. For security purposes,the Business Components manage all data storage and retrieval.

The iControl Business Components provide web services-based APIs thatapplication components use to access the Business Components'capabilities. Functions of application components include presentingintegrated security system service data to end-users, performingadministrative duties, and integrating with external systems andback-office applications.

The primary published APIs for the iConnect Business Components include,but are not limited to, the following:

-   -   A Registry Manager API 252 provides access to the Registry        Manager Business Component's functionality, allowing management        of networks and users.    -   A Network Manager API 254 provides access to the Network Manager        Business Component's functionality, allowing management of        devices on a network.    -   A Data Manager API 256 provides access to the Data Manager        Business Component's functionality, such as setting and        retrieving (current and historical) data about device states.    -   A Provisioning API 258 provides a simple way to create new        networks and configure initial default properties.

Each API of an embodiment includes two modes of access: Java API or XMLAPI. The XML APIs are published as web services so that they can beeasily accessed by applications or servers over a network. The Java APIsare a programmer-friendly wrapper for the XML APIs. Applicationcomponents and integrations written in Java should generally use theJava APIs rather than the XML APIs directly.

The iConnect Business Components also have an XML-based interface 260for quickly adding support for new devices to the integrated securitysystem. This interface 260, referred to as DeviceConnect 260, is aflexible, standards-based mechanism for defining the properties of newdevices and how they can be managed. Although the format is flexibleenough to allow the addition of any type of future device, pre-definedXML profiles are currently available for adding common types of devicessuch as sensors (SensorConnect), home security panels (PanelConnect) andIP cameras (CameraConnect).

The iConnect End-User Application Components deliver the user interfacesthat run on the different types of clients supported by the integratedsecurity system service. The components are written in portable JavaJ2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs),etc.) and they all interact with the iControl Business Components viathe published APIs.

The following End-User Application Components generate CSS-basedHTML/JavaScript that is displayed on the target client. Theseapplications can be dynamically branded with partner-specific logos andURL links (such as Customer Support, etc.). The End-User ApplicationComponents of an embodiment include, but are not limited to, thefollowing:

-   -   An iControl Activation Application 270 that delivers the first        application that a user sees when they set up the integrated        security system service. This wizard-based web browser        application securely associates a new user with a purchased        gateway and the other devices included with it as a kit (if        any). It primarily uses functionality published by the        Provisioning API.    -   An iControl Web Portal Application 272 runs on PC browsers and        delivers the web-based interface to the integrated security        system service. This application allows users to manage their        networks (e.g. add devices and create automations) as well as to        view/change device states, and manage pictures and videos.        Because of the wide scope of capabilities of this application,        it uses three different Business Component APIs that include the        Registry Manager API, Network Manager API, and Data Manager API,        but the embodiment is not so limited.    -   An iControl Mobile Portal 274 is a small-footprint web-based        interface that runs on mobile phones and PDAs. This interface is        optimized for remote viewing of device states and        pictures/videos rather than network management. As such, its        interaction with the Business Components is primarily via the        Data Manager API.    -   Custom portals and targeted client applications can be provided        that leverage the same Business Component APIs used by the above        applications.    -   A Content Manager Application Component 276 delivers content to        a variety of clients. It sends multimedia-rich user interface        components to widget container clients (both PC and        browser-based), as well as to advanced touchscreen keypad        clients. In addition to providing content directly to end-user        devices, the Content Manager 276 provides widget-based user        interface components to satisfy requests from other Application        Components such as the iControl Web 272 and Mobile 274 portals.

A number of Application Components are responsible for overallmanagement of the service. These pre-defined applications, referred toas Service Management Application Components, are configured to offeroff-the-shelf solutions for production management of the integratedsecurity system service including provisioning, overall servicemonitoring, customer support, and reporting, for example. The ServiceManagement Application Components of an embodiment include, but are notlimited to, the following:

-   -   A Service Management Application 280 allows service        administrators to perform activities associated with service        installation, scaling and monitoring/alerting. This application        interacts heavily with the Element Management System (EMS)        Business Component to execute its functionality, and also        retrieves its monitoring data from that component via protocols        such as SNMP MIBs.    -   A Kitting Application 282 is used by employees performing        service provisioning tasks. This application allows home        security and self-monitoring devices to be associated with        gateways during the warehouse kitting process.    -   A CSR Application and Report Generator 284 is used by personnel        supporting the integrated security system service, such as CSRs        resolving end-user issues and employees enquiring about overall        service usage. The push of new gateway firmware to deployed        gateways is also managed by this application.

The iConnect servers 104 also support custom-built integrations with aservice provider's existing OSS/BSS, CSR and service delivery systems290. Such systems can access the iConnect web services XML API totransfer data to and from the iConnect servers 104. These types ofintegrations can compliment or replace the PC browser-based ServiceManagement applications, depending on service provider needs.

As described above, the integrated security system of an embodimentincludes a gateway, or iHub. The gateway of an embodiment includes adevice that is deployed in the home or business and couples or connectsthe various third-party cameras, home security panels, sensors anddevices to the iConnect server over a WAN connection as described indetail herein. The gateway couples to the home network and communicatesdirectly with the home security panel in both wired and wireless sensorinstallations. The gateway is configured to be low-cost, reliable andthin so that it complements the integrated security system network-basedarchitecture.

The gateway supports various wireless protocols and can interconnectwith a wide range of home security control panels. Service providers andusers can then extend the system's capabilities by adding IP cameras,lighting modules and additional security devices. The gateway isconfigurable to be integrated into many consumer appliances, includingset-top boxes, routers and security panels. The small and efficientfootprint of the gateway enables this portability and versatility,thereby simplifying and reducing the overall cost of the deployment.

FIG. 61 is a block diagram of the gateway 102 including gateway softwareor applications, under an embodiment. The gateway software architectureis relatively thin and efficient, thereby simplifying its integrationinto other consumer appliances such as set-top boxes, routers, touchscreens and security panels. The software architecture also provides ahigh degree of security against unauthorized access. This sectiondescribes the various key components of the gateway softwarearchitecture.

The gateway application layer 302 is the main program that orchestratesthe operations performed by the gateway. The Security Engine 304provides robust protection against intentional and unintentionalintrusion into the integrated security system network from the outsideworld (both from inside the premises as well as from the WAN). TheSecurity Engine 304 of an embodiment comprises one or more sub-modulesor components that perform functions including, but not limited to, thefollowing:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the gateway and iConnect        server in order to prevent unauthorized spoofing and attacks.        Data sent from the iConnect server to the gateway application        (or vice versa) is digitally signed as an additional layer of        security. Digital signing provides both authentication and        validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The gateway provides for 128-bit        SSL encapsulation of the user picture and video data sent over        the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A gateway-enabled device is assigned a unique activation key for        activation with an iConnect server. This ensures that only valid        gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying gateway-enabled devices        have the knowledge that only a gateway with the correct serial        number and activation key can be activated for use with an        iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 allows for seamless and secureupdates to the gateway firmware through the iControl MaintenanceApplication on the server 104, providing a transparent, hassle-freemechanism for the service provider to deploy new features and bug fixesto the installed user base. The firmware download mechanism is tolerantof connection loss, power interruption and user interventions (bothintentional and unintentional). Such robustness reduces down time andcustomer support issues. Gateway firmware can be remotely downloadeither for one gateway at a time, a group of gateways, or in batches.

The Automations engine 308 manages the user-defined rules of interactionbetween the different devices (e.g. when door opens turn on the light).Though the automation rules are programmed and reside at theportal/server level, they are cached at the gateway level in order toprovide short latency between device triggers and actions.

DeviceConnect 310 includes definitions of all supported devices (e.g.,cameras, security panels, sensors, etc.) using a standardized plug-inarchitecture. The DeviceConnect module 310 offers an interface that canbe used to quickly add support for any new device as well as enablinginteroperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 is responsible for executing the user definedschedules (e.g., take a picture every five minutes; every day at 8 amset temperature to 65 degrees Fahrenheit, etc.). Though the schedulesare programmed and reside at the iConnect server level they are sent tothe scheduler within the gateway application. The Schedules Engine 318then interfaces with SensorConnect 312 to ensure that scheduled eventsoccur at precisely the desired time.

The Device Management module 320 is in charge of all discovery,installation and configuration of both wired and wireless IP devices(e.g., cameras, etc.) coupled or connected to the system. Networked IPdevices, such as those used in the integrated security system, requireuser configuration of many IP and security parameters—to simplify theuser experience and reduce the customer support burden, the devicemanagement module of an embodiment handles the details of thisconfiguration. The device management module also manages the videorouting module described below.

The video routing engine 322 is responsible for delivering seamlessvideo streams to the user with zero-configuration. Through a multi-step,staged approach the video routing engine uses a combination of UPnPport-forwarding, relay server routing and STUN/TURN peer-to-peerrouting.

FIG. 62 is a block diagram of components of the gateway 102, under anembodiment. Depending on the specific set of functionality desired bythe service provider deploying the integrated security system service,the gateway 102 can use any of a number of processors 402, due to thesmall footprint of the gateway application firmware. In an embodiment,the gateway could include the Broadcom BCM5354 as the processor forexample. In addition, the gateway 102 includes memory (e.g., FLASH 404,RAM 406, etc.) and any number of input/output (I/O) ports 408.

Referring to the WAN portion 410 of the gateway 102, the gateway 102 ofan embodiment can communicate with the iConnect server using a number ofcommunication types and/or protocols, for example Broadband 412, GPRS414 and/or Public Switched Telephone Network (PTSN) 416 to name a few.In general, broadband communication 412 is the primary means ofconnection between the gateway 102 and the iConnect server 104 and theGPRS/CDMA 414 and/or PSTN 416 interfaces acts as backup for faulttolerance in case the user's broadband connection fails for whateverreason, but the embodiment is not so limited.

Referring to the LAN portion 420 of the gateway 102, various protocolsand physical transceivers can be used to communicate to off-the-shelfsensors and cameras. The gateway 102 is protocol-agnostic andtechnology-agnostic and as such can easily support almost any devicenetworking protocol. The gateway 102 can, for example, support GE andHoneywell security RF protocols 422, Z-Wave 424, serial (RS232 andRS485) 426 for direct connection to security panels as well as WiFi 428(802.11b/g) for communication to WiFi cameras.

The integrated security system includes couplings or connections among avariety of IP devices or components, and the device management module isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system of an embodiment uses a “sandbox” network todiscover and manage all IP devices coupled or connected as components ofthe system. The IP devices of an embodiment include wired devices,wireless devices, cameras, interactive touchscreens, and security panelsto name a few. These devices can be wired via ethernet cable or Wifidevices, all of which are secured within the sandbox network, asdescribed below. The “sandbox” network is described in detail below.

FIG. 63 is a block diagram 500 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255-257 are coupled to the gateway 102 using a securenetwork coupling or connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption). Thenetwork coupling or connection between the gateway 102 and the networkdevices 255-257 is a private coupling or connection in that it issegregated from any other network couplings or connections. The gateway102 is coupled to the premise router/firewall 252 via a coupling with apremise LAN 250. The premise router/firewall 252 is coupled to abroadband modem 251, and the broadband modern 251 is coupled to a WAN200 or other network outside the premise. The gateway 102 thus enablesor forms a separate wireless network, or sub-network, that includes somenumber of devices and is coupled or connected to the LAN 250 of the hostpremises. The gateway sub-network can include, but is not limited to,any number of other devices like WiFi IP cameras, security panels (e.g.,IP-enabled), and security touchscreens, to name a few. The gateway 102manages or controls the sub-network separately from the LAN 250 andtransfers data and information between components of the sub-network andthe LAN 250/WAN 200, but is not so limited. Additionally, other networkdevices 254 can be coupled to the LAN 250 without being coupled to thegateway 102.

FIG. 64 is a block diagram 600 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255-257 are coupled to the gateway 102. The networkcoupling or connection between the gateway 102 and the network devices255-257 is a private coupling or connection in that it is segregatedfrom any other network couplings or connections. The gateway 102 iscoupled or connected between the premise router/firewall 252 and thebroadband modem 251. The broadband modem 251 is coupled to a WAN 200 orother network outside the premise, while the premise router/firewall 252is coupled to a premise LAN 250. As a result of its location between thebroadband modem 251 and the premise router/firewall 252, the gateway 102can be configured or function as the premise router routing specifieddata between the outside network (e.g., WAN 200) and the premiserouter/firewall 252 of the LAN 250. As described above, the gateway 102in this configuration enables or forms a separate wireless network, orsub-network, that includes the network or premise devices 255-257 and iscoupled or connected between the LAN 250 of the host premises and theWAN 200. The gateway sub-network can include, but is not limited to, anynumber of network or premise devices 255-257 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The gateway 102 manages or controls the sub-network separately fromthe LAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the gateway 102.

The examples described above with reference to FIGS. 5 and 6 arepresented only as examples of IP device integration. The integratedsecurity system is not limited to the type, number and/or combination ofIP devices shown and described in these examples, and any type, numberand/or combination of IP devices is contemplated within the scope ofthis disclosure as capable of being integrated with the premise network.

The integrated security system of an embodiment includes a touchscreen(also referred to as the iControl touchscreen or integrated securitysystem touchscreen), as described above, which provides core securitykeypad functionality, content management and presentation, and embeddedsystems design. The networked security touchscreen system of anembodiment enables a consumer or security provider to easily andautomatically install, configure and manage the security system andtouchscreen located at a customer premise. Using this system thecustomer may access and control the local security system, local IPdevices such as cameras, local sensors and control devices (such aslighting controls or pipe freeze sensors), as well as the local securitysystem panel and associated security sensors (such as door/window,motion, and smoke detectors). The customer premise may be a home,business, and/or other location equipped with a wired or wirelessbroadband IP connection.

The system of an embodiment includes a touchscreen with a configurablesoftware user interface and/or a gateway device (e.g., iHub) thatcouples or connects to a premise security panel through a wired orwireless connection, and a remote server that provides access to contentand information from the premises devices to a user when they are remotefrom the home. The touchscreen supports broadband and/or WAN wirelessconnectivity. In this embodiment, the touchscreen incorporates an IPbroadband connection (e.g., Wifi radio, Ethernet port, etc.), and/or acellular radio (e.g., GPRS/GSM, CDMA, WiMax, etc.). The touchscreendescribed herein can be used as one or more of a security systeminterface panel and a network user interface (UI) that provides aninterface to interact with a network (e.g., LAN, WAN, internet, etc.).

The touchscreen of an embodiment provides an integrated touchscreen andsecurity panel as an all-in-one device. Once integrated using thetouchscreen, the touchscreen and a security panel of a premise securitysystem become physically co-located in one device, and the functionalityof both may even be co-resident on the same CPU and memory (though thisis not required).

The touchscreen of an embodiment also provides an integrated IP videoand touchscreen UI. As such, the touchscreen supports one or morestandard video CODECs/players (e.g., H.264, Flash Video, MOV, MPEG4,M-JPEG, etc.). The touchscreen UI then provides a mechanism (such as acamera or video widget) to play video. In an embodiment the video isstreamed live from an IP video camera. In other embodiments the videocomprises video clips or photos sent from an IP camera or from a remotelocation.

The touchscreen of an embodiment provides a configurable user interfacesystem that includes a configuration supporting use as a securitytouchscreen. In this embodiment, the touchscreen utilizes a modular userinterface that allows components to be modified easily by a serviceprovider, an installer, or even the end user. Examples of such a modularapproach include using Flash widgets, HTML-based widgets, or otherdownloadable code modules such that the user interface of thetouchscreen can be updated and modified while the application isrunning. In an embodiment the touchscreen user interface modules can bedownloaded over the internet. For example, a new security configurationwidget can be downloaded from a standard web server, and the touchscreenthen loads such configuration app into memory, and inserts it in placeof the old security configuration widget. The touchscreen of anembodiment is configured to provide a self-install user interface.

Embodiments of the networked security touchscreen system describedherein include a touchscreen device with a user interface that includesa security toolbar providing one or more functions including arm,disarm, panic, medic, and alert. The touchscreen therefore includes atleast one screen having a separate region of the screen dedicated to asecurity toolbar. The security toolbar of an embodiment is present inthe dedicated region at all times that the screen is active.

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing home-basedfunctions. The home-based functions of an embodiment include managing,viewing, and/or controlling IP video cameras. In this embodiment,regions of the home screen are allocated in the foul′ of widget icons;these widget icons (e.g. for cameras, thermostats, lighting, etc)provide functionality for managing home systems. So, for example, adisplayed camera icon, when selected, launches a Camera Widget, and theCamera widget in turn provides access to video from one or more cameras,as well as providing the user with relevant camera controls (take apicture, focus the camera, etc.)

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing, viewing, and/orcontrolling internet-based content or applications. For example, theWidget Manager UI presents a region of the home screen (up to andincluding the entire home screen) where internet widgets icons such asweather, sports, etc. may be accessed). Each of these icons may beselected to launch their respective content services.

The touchscreen of an embodiment is integrated into a premise networkusing the gateway, as described above. The gateway as described hereinfunctions to enable a separate wireless network, or sub-network, that iscoupled, connected, or integrated with another network (e.g., WAN, LANof the host premises, etc.). The sub-network enabled by the gatewayoptimizes the installation process for IP devices, like the touchscreen,that couple or connect to the sub-network by segregating these IPdevices from other such devices on the network. This segregation of theIP devices of the sub-network further enables separate security andprivacy policies to be implemented for these IP devices so that, wherethe IP devices are dedicated to specific functions (e.g., security), thesecurity and privacy policies can be tailored specifically for thespecific functions. Furthermore, the gateway and the sub-network itforms enables the segregation of data traffic, resulting in faster andmore efficient data flow between components of the host network,components of the sub-network, and between components of the sub-networkand components of the network.

The touchscreen of an embodiment includes a core functional embeddedsystem that includes an embedded operating system, required hardwaredrivers, and an open system interface to name a few. The core functionalembedded system can be provided by or as a component of a conventionalsecurity system (e.g., security system available from GE Security).These core functional units are used with components of the integratedsecurity system as described herein. Note that portions of thetouchscreen description below may include reference to a host premisesecurity system (e.g., GE security system), but these references areincluded only as an example and do not limit the touchscreen tointegration with any particular security system.

As an example, regarding the core functional embedded system, a reducedmemory footprint version of embedded Linux forms the core operatingsystem in an embodiment, and provides basic TCP/IP stack and memorymanagement functions, along with a basic set of low-level graphicsprimitives. A set of device drivers is also provided or included thatoffer low-level hardware and network interfaces. In addition to thestandard drivers, an interface to the RS 485 bus is included thatcouples or connects to the security system panel (e.g., GE Concordpanel). The interface may, for example, implement the Superbus 2000protocol, which can then be utilized by the more comprehensivetransaction-level security functions implemented in PanelConnecttechnology (e.g SetAlarmLevel (int level, int partition, char*accessCode)). Power control drivers are also provided.

FIG. 65 is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment. The touchscreen 700 generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700 alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, PanelConnect API 724, a gatewayinterface 726, and one or more ports 728.

More specifically, the touchscreen, when configured as a home securitydevice, includes but is not limited to the following application orsoftware modules: RS 485 and/or RS-232 bus security protocols toconventional home security system panel (e.g., GE Concord panel);functional home security classes and interfaces (e.g. Panel ARM state,Sensor status, etc.); Application/Presentation layer or engine; ResidentApplication; Consumer Home Security Application; installer home securityapplication; core engine; and System bootloader/Software Updater. Thecore Application engine and system bootloader can also be used tosupport other advanced content and applications. This provides aseamless interaction between the premise security application and otheroptional services such as weather widgets or IP cameras.

An alternative configuration of the touchscreen includes a firstApplication engine for premise security and a second Application enginefor all other applications. The integrated security system applicationengine supports content standards such as HTML, XML, Flash, etc. andenables a rich consumer experience for all ‘widgets’, whethersecurity-based or not. The touchscreen thus provides service providersthe ability to use web content creation and management tools to buildand download any ‘widgets’ regardless of their functionality.

As discussed above, although the Security Applications have specificlow-level functional requirements in order to interface with the premisesecurity system, these applications make use of the same fundamentalapplication facilities as any other ‘widget’, application facilitiesthat include graphical layout, interactivity, application handoff,screen management, and network interfaces, to name a few.

Content management in the touchscreen provides the ability to leverageconventional web development tools, performance optimized for anembedded system, service provider control of accessible content, contentreliability in a consumer device, and consistency between ‘widgets’ andseamless widget operational environment. In an embodiment of theintegrated security system, widgets are created by web developers andhosted on the integrated security system Content Manager (and stored inthe Content Store database). In this embodiment the server componentcaches the widgets and offers them to consumers through the web-basedintegrated security system provisioning system. The servers interactwith the advanced touchscreen using HTTPS interfaces controlled by thecore engine and dynamically download widgets and updates as needed to becached on the touchscreen. In other embodiments widgets can be accesseddirectly over a network such as the Internet without needing to gothrough the iControl Content Manager

Referring to FIG. 65, the touchscreen system is built on a tieredarchitecture, with defined interfaces between theApplication/Presentation Layer (the Application Engine) on the top, theCore Engine in the middle, and the security panel and gateway APIs atthe lower level. The architecture is configured to provide maximumflexibility and ease of maintenance.

The application engine of the touchscreen provides the presentation andinteractivity capabilities for all applications (widgets) that run onthe touchscreen, including both core security function widgets and thirdparty content widgets. FIG. 66 is an example screenshot 800 of anetworked security touchscreen, under an embodiment. This examplescreenshot 800 includes three interfaces or user interface (UI)components 802-806, but is not so limited. A first UI 802 of thetouchscreen includes icons by which a user controls or accessesfunctions and/or components of the security system (e.g., “Main”,“Panic”, “Medic”, “Fire”, state of the premise alarm system (e.g.,disarmed, armed, etc.), etc.); the first UI 802, which is also referredto herein as a security interface, is always presented on thetouchscreen. A second UI 804 of the touchscreen includes icons by whicha user selects or interacts with services and other network content(e.g., clock, calendar, weather, stocks, news, sports, photos, maps,music, etc.) that is accessible via the touchscreen. The second UI 804is also referred to herein as a network interface or content interface.A third UI 806 of the touchscreen includes icons by which a user selectsor interacts with additional services or componets (e.g., intercomcontrol, security, cameras coupled to the system in particular regions(e.g., front door, baby, etc.) available via the touchscreen.

A component of the application engine is the Presentation Engine, whichincludes a set of libraries that implement the standards-based widgetcontent (e.g., XML, HTML, JavaScript, Flash) layout and interactivity.This engine provides the widget with interfaces to dynamically load bothgraphics and application logic from third parties, support high leveldata description language as well as standard graphic formats. The setof web content-based functionality available to a widget developer isextended by specific touchscreen functions implemented as local webservices by the Core Engine.

The resident application of the touchscreen is the master service thatcontrols the interaction of all widgets in the system, and enforces thebusiness and security rules required by the service provider. Forexample, the resident application determines the priority of widgets,thereby enabling a home security widget to override resource requestsfrom a less critical widget (e.g. a weather widget). The residentapplication also monitors widget behavior, and responds to client orserver requests for cache updates.

The core engine of the touchscreen manages interaction with othercomponents of the integrated security system, and provides an interfacethrough which the resident application and authorized widgets can getinformation about the home security system, set alarms, install sensors,etc. At the lower level, the Core Engine's main interactions are throughthe PanelConnect API, which handles all communication with the securitypanel, and the gateway Interface, which handles communication with thegateway. In an embodiment, both the iHub Interface and PanelConnect APIare resident and operating on the touchscreen. In another embodiment,the PanelConnect API runs on the gateway or other device that providessecurity system interaction and is accessed by the touchscreen through aweb services interface.

The Core Engine also handles application and service level persistentand cached memory functions, as well as the dynamic provisioning ofcontent and widgets, including but not limited to: flash memorymanagement, local widget and content caching, widget version management(download, cache flush new/old content versions), as well as the cachingand synchronization of user preferences. As a portion of these servicesthe Core engine incorporates the bootloader functionality that isresponsible for maintaining a consistent software image on thetouchscreen, and acts as the client agent for all software updates. Thebootloader is configured to ensure full update redundancy so thatunsuccessful downloads cannot corrupt the integrated security system.

Video management is provided as a set of web services by the CoreEngine. Video management includes the retrieval and playback of localvideo feeds as well as remote control and management of cameras (allthrough iControl CameraConnect technology).

Both the high level application layer and the mid-level core engine ofthe touchscreen can make calls to the network. Any call to the networkmade by the application layer is automatically handed off to a localcaching proxy, which determines whether the request should be handledlocally. Many of the requests from the application layer are webservices API requests, although such requests could be satisfied by theiControl servers, they are handled directly by the touchscreen and thegateway. Requests that get through the caching proxy are checked againsta white list of acceptable sites, and, if they match, are sent offthrough the network interface to the gateway. Included in the NetworkSubsystem is a set of network services including HTTP, HTTPS, andserver-level authentication functions to manage the secure client-serverinterface. Storage and management of certificates is incorporated as apart of the network services layer.

Server components of the integrated security system servers supportinteractive content services on the touchscreen. These server componentsinclude, but are not limited to the content manager, registry manager,network manager, and global registry, each of which is described herein.

The Content Manager oversees aspects of handling widget data and rawcontent on the touchscreen. Once created and validated by the serviceprovider, widgets are ‘ingested’ to the Content Manager, and then becomeavailable as downloadable services through the integrated securitysystem Content Management APIs. The Content manager maintains versionsand timestamp information, and connects to the raw data contained in thebackend Content Store database. When a widget is updated (or new contentbecomes available) all clients registering interest in a widget aresystematically updated as needed (a process that can be configured at anaccount, locale, or system-wide level).

The Registry Manager handles user data, and provisioning accounts,including information about widgets the user has decided to install, andthe user preferences for these widgets.

The Network Manager handles getting and setting state for all devices onthe integrated security system network (e.g., sensors, panels, cameras,etc.). The Network manager synchronizes with the gateway, the advancedtouchscreen, and the subscriber database.

The Global Registry is a primary starting point server for all clientservices, and is a logical referral service that abstracts specificserver locations/addresses from clients (touchscreen, gateway 102,desktop widgets, etc.). This approach enables easy scaling/migration ofserver farms.

The touchscreen of an embodiment operates wirelessly with a premisesecurity system. The touchscreen of an embodiment incorporates an RFtransceiver component that either communicates directly with the sensorsand/or security panel over the panel's proprietary RF frequency, or thetouchscreen communicates wirelessly to the gateway over 802.11,Ethernet, or other IP-based communications channel, as described indetail herein. In the latter case the gateway implements thePanelConnect interface and communicates directly to the security paneland/or sensors over wireless or wired networks as described in detailabove.

The touchscreen of an embodiment is configured to operate with multiplesecurity systems through the use of an abstracted security systeminterface. In this embodiment, the PanelConnect API can be configured tosupport a plurality of proprietary security system interfaces, eithersimultaneously or individually as described herein. In one embodiment ofthis approach, the touchscreen incorporates multiple physical interfacesto security panels (e.g. GE Security RS-485, Honeywell RF, etc.) inaddition to the PanelConnect API implemented to support multiplesecurity interfaces. The change needed to support this in PanelConnectis a configuration parameter specifying the panel type connection thatis being utilized.

So for example, the setARMState( ) function is called with an additionalparameter (e.g., Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”, panelType=“GE Concord4 RS485”)).The ‘panelType’ parameter is used by the setARMState function (and inpractice by all of the PanelConnect functions) to select an algorithmappropriate to the specific panel out of a plurality of alogorithms.

The touchscreen of an embodiment is self-installable. Consequently, thetouchscreen provides a ‘wizard’ approach similar to that used intraditional computer installations (e.g. InstallShield). The wizard canbe resident on the touchscreen, accessible through a web interface, orboth. In one embodiment of a touchscreen self-installation process, theservice provider can associate devices (sensors, touchscreens, securitypanels, lighting controls, etc.) remotely using a web-basedadministrator interface.

The touchscreen of an embodiment includes a battery backup system for asecurity touchscreen. The touchscreen incorporates a standard Li-ion orother battery and charging circuitry to allow continued operation in theevent of a power outage. In an embodiment the battery is physicallylocated and connected within the touchscreen enclosure. In anotherembodiment the battery is located as a part of the power transformer, orin between the power transformer and the touchscreen.

The example configurations of the integrated security system describedabove with reference to FIGS. 5 and 6 include a gateway that is aseparate device, and the touchscreen couples to the gateway. However, inan alternative embodiment, the gateway device and its functionality canbe incorporated into the touchscreen so that the device managementmodule, which is now a component of or included in the touchscreen, isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system with the integrated touchscreen/gateway usesthe same “sandbox” network to discover and manage all IP devices coupledor connected as components of the system.

The touchscreen of this alternative embodiment integrates the componentsof the gateway with the components of the touchscreen as describedherein. More specifically, the touchscreen of this alternativeembodiment includes software or applications described above withreference to FIG. 3. In this alternative embodiment, the touchscreenincludes the gateway application layer 302 as the main program thatorchestrates the operations performed by the gateway. A Security Engine304 of the touchscreen provides robust protection against intentionaland unintentional intrusion into the integrated security system networkfrom the outside world (both from inside the premises as well as fromthe WAN). The Security Engine 304 of an embodiment comprises one or moresub-modules or components that perform functions including, but notlimited to, the following:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the touchscreen and        iConnect server in order to prevent unauthorized spoofing and        attacks. Data sent from the iConnect server to the gateway        application (or vice versa) is digitally signed as an additional        layer of security. Digital signing provides both authentication        and validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The touchscreen provides for        128-bit SSL encapsulation of the user picture and video data        sent over the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A touchscreen-enabled device is assigned a unique activation key        for activation with an iConnect server. This ensures that only        valid gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying touchscreen-enabled        devices have the knowledge that only a gateway with the correct        serial number and activation key can be activated for use with        an iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 of the touchscreen allows forseamless and secure updates to the gateway firmware through the iControlMaintenance Application on the server 104, providing a transparent,hassle-free mechanism for the service provider to deploy new featuresand bug fixes to the installed user base. The firmware downloadmechanism is tolerant of connection loss, power interruption and userinterventions (both intentional and unintentional). Such robustnessreduces down time and customer support issues. Touchscreen firmware canbe remotely download either for one touchscreen at a time, a group oftouchscreen, or in batches.

The Automations engine 308 of the touchscreen manages the user-definedrules of interaction between the different devices (e.g. when door opensturn on the light). Though the automation rules are programmed andreside at the portal/server level, they are cached at the gateway levelin order to provide short latency between device triggers and actions.

DeviceConnect 310 of the touchscreen touchscreen includes definitions ofall supported devices (e.g., cameras, security panels, sensors, etc.)using a standardized plug-in architecture. The DeviceConnect module 310offers an interface that can be used to quickly add support for any newdevice as well as enabling interoperability between devices that usedifferent technologies/protocols. For common device types, pre-definedsub-modules have been defined, making supporting new devices of thesetypes even easier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 of the touchscreen is responsible for executingthe user defined schedules (e.g., take a picture every five minutes;every day at 8 am set temperature to 65 degrees Fahrenheit, etc.).Though the schedules are programmed and reside at the iConnect serverlevel they are sent to the scheduler within the gateway application ofthe touchscreen. The Schedules Engine 318 then interfaces withSensorConnect 312 to ensure that scheduled events occur at precisely thedesired time.

The Device Management module 320 of the touchscreen is in charge of alldiscovery, installation and configuration of both wired and wireless IPdevices (e.g., cameras, etc.) coupled or connected to the system.Networked IP devices, such as those used in the integrated securitysystem, require user configuration of many IP and security parameters,and the device management module of an embodiment handles the details ofthis configuration. The device management module also manages the videorouting module described below.

The video routing engine 322 of the touchscreen is responsible fordelivering seamless video streams to the user with zero-configuration.Through a multi-step, staged approach the video routing engine uses acombination of UPnP port-forwarding, relay server routing and STUN/TURNpeer-to-peer routing. The video routing engine is described in detail inthe Related Applications.

FIG. 67 is a block diagram 900 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255, 256, 957 are coupled to the touchscreen 902 using asecure network connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption), andthe touchscreen 902 coupled to the premise router/firewall 252 via acoupling with a premise LAN 250. The premise router/firewall 252 iscoupled to a broadband modem 251, and the broadband modem 251 is coupledto a WAN 200 or other network outside the premise. The touchscreen 902thus enables or forms a separate wireless network, or sub-network, thatincludes some number of devices and is coupled or connected to the LAN250 of the host premises. The touchscreen sub-network can include, butis not limited to, any number of other devices like WiFi IP cameras,security panels (e.g., IP-enabled), and IP devices, to name a few. Thetouchscreen 902 manages or controls the sub-network separately from theLAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 902.

FIG. 68 is a block diagram 1000 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255, 256, 1057 are coupled to the touchscreen 1002,and the touchscreen 1002 is coupled or connected between the premiserouter/firewall 252 and the broadband modem 251. The broadband modem 251is coupled to a WAN 200 or other network outside the premise, while thepremise router/firewall 252 is coupled to a premise LAN 250. As a resultof its location between the broadband modem 251 and the premiserouter/firewall 252, the touchscreen 1002 can be configured or functionas the premise router routing specified data between the outside network(e.g., WAN 200) and the premise router/firewall 252 of the LAN 250. Asdescribed above, the touchscreen 1002 in this configuration enables orforms a separate wireless network, or sub-network, that includes thenetwork or premise devices 255, 156, 1057 and is coupled or connectedbetween the LAN 250 of the host premises and the WAN 200. Thetouchscreen sub-network can include, but is not limited to, any numberof network or premise devices 255, 256, 1057 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The touchscreen 1002 manages or controls the sub-network separatelyfrom the LAN 250 and transfers data and information between componentsof the sub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 1002.

The gateway of an embodiment, whether a stand-along component orintegrated with a touchscreen, enables couplings or connections and thusthe flow or integration of information between various components of thehost premises and various types and/or combinations of IP devices, wherethe components of the host premises include a network (e.g., LAN) and/ora security system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

The gateway of an embodiment, as described herein, enables couplings orconnections and thus the flow of information between various componentsof the host premises and various types and/or combinations of IPdevices, where the components of the host premises include a network, asecurity system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

FIG. 69 is a flow diagram for a method 1100 of forming a securitynetwork including integrated security system components, under anembodiment. Generally, the method comprises coupling 1102 a gatewaycomprising a connection management component to a local area network ina first location and a security server in a second location. The methodcomprises forming 1104 a security network by automatically establishinga wireless coupling between the gateway and a security system using theconnection management component. The security system of an embodimentcomprises security system components located at the first location. Themethod comprises integrating 1106 communications and functions of thesecurity system components into the security network via the wirelesscoupling.

FIG. 70 is a flow diagram for a method 1200 of forming a securitynetwork including integrated security system components and networkdevices, under an embodiment. Generally, the method comprises coupling1202 a gateway to a local area network located in a first location and asecurity server in a second location. The method comprises automaticallyestablishing 1204 communications between the gateway and security systemcomponents at the first location, the security system including thesecurity system components. The method comprises automaticallyestablishing 1206 communications between the gateway and premise devicesat the first location. The method comprises forming 1208 a securitynetwork by electronically integrating, via the gateway, communicationsand functions of the premise devices and the security system components.

In an example embodiment, FIG. 71 is a flow diagram 1300 for integrationor installation of an IP device into a private network environment,under an embodiment. The IP device includes any IP-capable device that,for example, includes the touchscreen of an embodiment. The variables ofan embodiment set at time of installation include, but are not limitedto, one or more of a private SSID/Password, a gateway identifier, asecurity panel identifier, a user account TS, and a Central MonitoringStation account identification.

An embodiment of the IP device discovery and management begins with auser or installer activating 1302 the gateway and initiating 1304 theinstall mode of the system. This places the gateway in an install mode.Once in install mode, the gateway shifts to a default (Install) Wificonfiguration. This setting will match the default setting for otherintegrated security system-enabled devices that have been pre-configuredto work with the integrated security system. The gateway will then beginto provide 1306 DHCP addresses for these IP devices. Once the deviceshave acquired a new DHCP address from the gateway, those devices areavailable for configuration into a new secured Wifi network setting.

The user or installer of the system selects 1308 all devices that havebeen identified as available for inclusion into the integrated securitysystem. The user may select these devices by their unique IDs via a webpage, Touchscreen, or other client interface. The gateway provides 1310data as appropriate to the devices. Once selected, the devices areconfigured 1312 with appropriate secured Wifi settings, including SSIDand WPA/WPA-2 keys that are used once the gateway switches back to thesecured sandbox configuration from the “Install” settings. Othersettings are also configured as appropriate for that type of device.Once all devices have been configured, the user is notified and the usercan exit install mode. At this point all devices will have beenregistered 1314 with the integrated security system servers.

The installer switches 1316 the gateway to an operational mode, and thegateway instructs or directs 1318 all newly configured devices to switchto the “secured” Wifi sandbox settings. The gateway then switches 1320to the “secured” Wifi settings. Once the devices identify that thegateway is active on the “secured” network, they request new DHCPaddresses from the gateway which, in response, provides 1322 the newaddresses. The devices with the new addresses are then operational 1324on the secured network.

In order to ensure the highest level of security on the secured network,the gateway can create or generate a dynamic network securityconfiguration based on the unique ID and private key in the gateway,coupled with a randomizing factor that can be based on online time orother inputs. This guarantees the uniqueness of the gateway securednetwork configuration.

To enable the highest level of performance, the gateway analyzes the RFspectrum of the 802.11x network and determines which frequencyband/channel it should select to run.

An alternative embodiment of the camera/IP device management processleverages the local ethernet connection of the sandbox network on thegateway. This alternative process is similar to the Wifi discoveryembodiment described above, except the user connects the targeted deviceto the ethernet port of the sandbox network to begin the process. Thisalternative embodiment accommodates devices that have not beenpre-configured with the default “Install” configuration for theintegrated security system.

This alternative embodiment of the IP device discovery and managementbegins with the user/installer placing the system into install mode. Theuser is instructed to attach an IP device to be installed to the sandboxEthernet port of the gateway. The IP device requests a DHCP address fromthe gateway which, in response to the request, provides the address. Theuser is presented the device and is asked if he/she wants to install thedevice. If yes, the system configures the device with the secured Wifisettings and other device-specific settings (e.g., camera settings forvideo length, image quality etc.). The user is next instructed todisconnect the device from the ethernet port. The device is nowavailable for use on the secured sandbox network.

FIG. 72 is a block diagram showing communications among integrated IPdevices of the private network environment, under an embodiment. The IPdevices of this example include a security touchscreen 1403, gateway1402 (e.g., “iHub”), and security panel (e.g., “Security Panel 1”,“Security Panel 2”, “Security Panel n”), but the embodiment is not solimited. In alternative embodiments any number and/or combination ofthese three primary component types may be combined with othercomponents including IP devices and/or security system components. Forexample, a single device that comprises an integrated gateway,touchscreen, and security panel is merely another embodiment of theintegrated security system described herein. The description thatfollows includes an example configuration that includes a touchscreenhosting particular applications. However, the embodiment is not limitedto the touchscreen hosting these applications, and the touchscreenshould be thought of as representing any IP device.

Referring to FIG. 14, the touchscreen 1403 incorporates an application1410 that is implemented as computer code resident on the touchscreenoperating system, or as a web-based application running in a browser, oras another type of scripted application (e.g., Flash, Java, VisualBasic, etc.). The touchscreen core application 1410 represents thisapplication, providing user interface and logic for the end user tomanage their security system or to gain access to networked informationor content (Widgets). The touchscreen core application 1410 in turnaccesses a library or libraries of functions to control the localhardware (e.g. screen display, sound, LEDs, memory, etc.) as well asspecialized librarie(s) to couple or connect to the security system.

In an embodiment of this security system connection, the touchscreen1403 communicates to the gateway 1402, and has no direct communicationwith the security panel. In this embodiment, the touchscreen coreapplication 1410 accesses the remote service APIs 1412 which providesecurity system functionality (e.g. ARM/DISARM panel, sensor state,get/set panel configuration parameters, initiate or get alarm events,etc.). In an embodiment, the remote service APIs 1412 implement one ormore of the following functions, but the embodiment is not so limited:Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”);sensorState=getSensors(type=“ALL|SensorName|SensorNameList”);result=setSensorState(SensorName, parameters=“Option1, Options2, . . .Option n”); interruptHandler=SensorEvent( ); and,interruptHandler=alarmEvent( ).

Functions of the remote service APIs 1412 of an embodiment use a remotePanelConnect API 1424 which resides in memory on the gateway 1402. Thetouchscreen 1403 communicates with the gateway 1402 through a suitablenetwork interface such as an Ethernet or 802.11 RF connection, forexample. The remote PanelConnect API 1424 provides the underlyingSecurity System Interfaces 1426 used to communicate with and control oneor more types of security panel via wired link 1430 and/or RF link 3.The PanelConnect API 1224 provides responses and input to the remoteservices APIs 1426, and in turn translates function calls and data toand from the specific protocols and functions supported by a specificimplementation of a Security Panel (e.g. a GE Security Simon XT orHoneywell Vista 20P). In an embodiment, the PanelConnect API 1224 uses a345 MHz RF transceiver or receiver hardware/firmware module tocommunicate wirelessly to the security panel and directly to a set of345 MHz RF-enabled sensors and devices, but the embodiment is not solimited.

The gateway of an alternative embodiment communicates over a wiredphysical coupling or connection to the security panel using the panel'sspecific wired hardware (bus) interface and the panel's bus-levelprotocol.

In an alternative embodiment, the Touchscreen 1403 implements the samePanelConnect API 1414 locally on the Touchscreen 1403, communicatingdirectly with the Security Panel 2 and/or Sensors 2 over the proprietaryRF link or over a wired link for that system. In this embodiment theTouchscreen 1403, instead of the gateway 1402, incorporates the 345 MHzRF transceiver to communicate directly with Security Panel 2 or Sensors2 over the RF link 2. In the case of a wired link the Touchscreen 1403incorporates the real-time hardware (e.g. a PIC chip and RS232-variantserial link) to physically connect to and satisfy the specific bus-leveltiming requirements of the SecurityPanel2.

In yet another alternative embodiment, either the gateway 1402 or theTouchscreen 1403 implements the remote service APIs. This embodimentincludes a Cricket device (“Cricket”) which comprises but is not limitedto the following components: a processor (suitable for handling 802.11protocols and processing, as well as the bus timing requirements ofSecurityPanel1); an 802.11 (WiFi) client IP interface chip; and, aserial bus interface chip that implements variants of RS232 or RS485,depending on the specific Security Panel.

The Cricket also implements the full PanelConnect APIs such that it canperform the same functions as the case where the gateway implements thePanelConnect APIs. In this embodiment, the touchscreen core application1410 calls functions in the remote service APIs 1412 (such assetArmState( )). These functions in turn couple or connect to the remoteCricket through a standard IP connection (“Cricket IP Link”) (e.g.,Ethernet, Homeplug, the gateway's proprietary Wifi network, etc.). TheCricket in turn implements the PanelConnect API, which responds to therequest from the touchscreen core application, and performs theappropriate function using the proprietary panel interface. Thisinterface uses either the wireless or wired proprietary protocol for thespecific security panel and/or sensors.

FIG. 73 is a flow diagram of a method of integrating an external controland management application system with an existing security system,under an embodiment. Operations begin when the system is powered on1510, involving at a minimum the power-on of the gateway device, andoptionally the power-on of the connection between the gateway device andthe remote servers. The gateway device initiates 1520 a software and RF′sequence to locate the extant security system. The gateway and installerinitiate and complete 1530 a sequence to ‘learn’ the gateway into thesecurity system as a valid and authorized control device. The gatewayinitiates 1540 another software and RF sequence of instructions todiscover and learn the existence and capabilities of existing RF deviceswithin the extant security system, and store this information in thesystem. These operations under the system of an embodiment are describedin further detail below.

Unlike conventional systems that extend an existing security system, thesystem of an embodiment operates utilizing the proprietary wirelessprotocols of the security system manufacturer. In one illustrativeembodiment, the gateway is an embedded computer with an IP LAN and WANconnection and a plurality of RF transceivers and software protocolmodules capable of communicating with a plurality of security systemseach with a potentially different RF and software protocol interface.After the gateway has completed the discovery and learning 1540 ofsensors and has been integrated 1550 as a virtual control device in theextant security system, the system becomes operational. Thus, thesecurity system and associated sensors are presented 1550 as accessibledevices to a potential plurality of user interface subsystems.

The system of an embodiment integrates 1560 the functionality of theextant security system with other non-security devices including but notlimited to IP cameras, touchscreens, lighting controls, door lockingmechanisms, which may be controlled via RF, wired or powerline-basednetworking mechanisms supported by the gateway or servers.

The system of an embodiment provides a user interface subsystem 1570enabling a user to monitor, manage, and control the system andassociated sensors and security systems. In an embodiment of the system,a user interface subsystem is an HTML/XML/Javascript/Java/AJAX/Flashpresentation of a monitoring and control application, enabling users toview the state of all sensors and controllers in the extant securitysystem from a web browser or equivalent operating on a computer, PDA,mobile phone, or other consumer device.

In another illustrative embodiment of the system described herein, auser interface subsystem is an HTML/XML/Javascript/Java/AJAXpresentation of a monitoring and control application, enabling users tocombine the monitoring and control of the extant security system andsensors with the monitoring and control of non-security devicesincluding but not limited to IP cameras, touchscreens, lightingcontrols, door locking mechanisms.

In another illustrative embodiment of the system described herein, auser interface subsystem is a mobile phone application enabling users tomonitor and control the extant security system as well as othernon-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application running on a keypad ortouchscreen device enabling users to monitor and control the extantsecurity system as well as other non-security devices.

In another illustrative embodiment of the system described herein, auser interface subsystem is an application operating on a TV or set-topbox connected to a TV enabling users to monitor and control the extantsecurity system as well as other non-security devices.

FIG. 74 is a block diagram of an integrated security system 1600wirelessly interfacing to proprietary security systems, under anembodiment. A security system 1610 is coupled or connected to a Gateway1620, and from Gateway 1620 coupled or connected to a plurality ofinformation and content sources across a network 1630 including one ormore web servers 1640, system databases 1650, and applications servers1660. While in one embodiment network 1630 is the Internet, includingthe World Wide Web, those of skill in the art will appreciate thatnetwork 1630 may be any type of network, such as an intranet, anextranet, a virtual private network (VPN), a mobile network, or anon-TCP/IP based network.

Moreover, other elements of the system of an embodiment may beconventional, well-known elements that need not be explained in detailherein. For example, security system 1610 could be any type home orbusiness security system, such devices including but not limited to astandalone RF home security system or a non-RF-capable wired homesecurity system with an add-on RF interface module. In the integratedsecurity system 1600 of this example, security system 1610 includes anRF-capable wireless security panel (WSP) 1611 that acts as the mastercontroller for security system 1610. Well-known examples of such a WSPinclude the GE Security Concord, Networx, and Simon panels, theHoneywell Vista and Lynx panels, and similar panels from DSC and Napco,to name a few. A wireless module 1614 includes the RF hardware andprotocol software necessary to enable communication with and control ofa plurality of wireless devices 1613. WSP 1611 may also manage wireddevices 1614 physically connected to WSP 1611 with an RS232 or RS485 orEthernet connection or similar such wired interface.

In an implementation consistent with the systems and methods describedherein, Gateway 1620 provides the interface between security system 1610and LAN and/or WAN for purposes of remote control, monitoring, andmanagement. Gateway 1620 communicates with an external web server 1640,database 1650, and application server 1660 over network 1630 (which maycomprise WAN, LAN, or a combination thereof). In this example system,application logic, remote user interface functionality, as well as userstate and account are managed by the combination of these remoteservers. Gateway 1620 includes server connection manager 1621, asoftware interface module responsible for all server communication overnetwork 1630. Event manager 1622 implements the main event loop forGateway 1620, processing events received from device manager 1624(communicating with non-security system devices including but notlimited to IP cameras, wireless thermostats, or remote door locks).Event manager 1622 further processes events and control messages fromand to security system 1610 by utilizing WSP manager 1623.

WSP manager 1623 and device manager 1624 both rely upon wirelessprotocol manager 1626 which receives and stores the proprietary orstandards-based protocols required to support security system 1610 aswell as any other devices interfacing with gateway 1620. WSP manager1623 further utilizes the comprehensive protocols and interfacealgorithms for a plurality of security systems 1610 stored in the WSP DBclient database associated with wireless protocol manager 1626. Thesevarious components implement the software logic and protocols necessaryto communicate with and manager devices and security systems 1610.Wireless Transceiver hardware modules 1625 are then used to implementthe physical RF communications link to such devices and security systems1610. An illustrative wireless transceiver 1625 is the GE SecurityDialog circuit board, implementing a 319.5 MHz two-way RF transceivermodule. In this example, RF Link 1670 represents the 319.5 MHz RFcommunication link, enabling gateway 1620 to monitor and control WSP1611 and associated wireless and wired devices 1613 and 1614,respectively.

In one embodiment, server connection manager 1621 requests and receivesa set of wireless protocols for a specific security system 1610 (anillustrative example being that of the GE Security Concord panel andsensors) and stores them in the WSP DB portion of the wireless protocolmanager 1626. WSP manager 1623 then utilizes such protocols fromwireless protocol manager 1626 to initiate the sequence of processesdetailed in FIG. 15 and FIG. 16 for learning gateway 1620 into securitysystem 1610 as an authorized control device. Once learned in, asdescribed with reference to FIG. 16 (and above), event manager 1622processes all events and messages detected by the combination of WSPmanager 1623 and the GE Security wireless transceiver module 1625.

In another embodiment, gateway 1620 incorporates a plurality of wirelesstransceivers 1625 and associated protocols managed by wireless protocolmanager 1626. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1611, wireless devices1613, and wired devices 1614. For example a wireless sensor from onemanufacturer may be utilized to control a device using a differentprotocol from a different manufacturer.

In another embodiment, gateway 1620 incorporates a wired interface tosecurity system 1610, and incorporates a plurality of wirelesstransceivers 1625 and associated protocols managed by wireless protocolmanager 1626. In this embodiment events and control of multipleheterogeneous devices may be coordinated with WSP 1611, wireless devices1613, and wired devices 1614.

Of course, while an illustrative embodiment of an architecture of thesystem of an embodiment is described in detail herein with respect toFIG. 16, one of skill in the art will understand that modifications tothis architecture may be made without departing from the scope of thedescription presented herein. For example, the functionality describedherein may be allocated differently between client and server, oramongst different server or processor-based components. Likewise, theentire functionality of the gateway 1620 described herein could beintegrated completely within an existing security system 1610. In suchan embodiment, the architecture could be directly integrated with asecurity system 1610 in a manner consistent with the currently describedembodiments.

FIG. 75 is a flow diagram for wirelessly ‘learning’ the Gateway into anexisting security system and discovering extant sensors, under anembodiment. The learning interfaces gateway 1620 with security system1610. Gateway 1620 powers up 1710 and initiates software sequences 1720and 1725 to identify accessible WSPs 1611 and wireless devices 1613,respectively (e.g., one or more WSPs and/or devices within range ofgateway 1620). Once identified, WSP 1611 is manually or automaticallyset into ‘learn mode’ 1730, and gateway 1620 utilizes availableprotocols to add 1740 itself as an authorized control device in securitysystem 1610. Upon successful completion of this task, WSP 1611 ismanually or automatically removed from ‘learn mode’ 1750.

Gateway 1620 utilizes the appropriate protocols to mimic 1760 the firstidentified device 1614. In this operation gateway 1620 identifies itselfusing the unique or pseudo-unique identifier of the first found device1614, and sends an appropriate change of state message over RF Link1670. In the event that WSP 1611 responds to this change of statemessage, the device 1614 is then added 1770 to the system in database1650. Gateway 1620 associates 1780 any other information (such as zonename or token-based identifier) with this device 1614 in database 1650,enabling gateway 1620, user interface modules, or any application toretrieve this associated information.

In the event that WSP 1611 does not respond to the change of statemessage, the device 1614 is not added 1770 to the system in database1650, and this device 1614 is identified as not being a part of securitysystem 1610 with a flag, and is either ignored or added as anindependent device, at the discretion of the system provisioning rules.Operations hereunder repeat 1785 operations 1760, 1770, 1780 for alldevices 1614 if applicable. Once all devices 1614 have been tested inthis way, the system begins operation 1790.

In another embodiment, gateway 1620 utilizes a wired connection to WSP1611, but also incorporates a wireless transceiver 1625 to communicatedirectly with devices 1614. In this embodiment, operations under 1720above are removed, and operations under 1740 above are modified so thesystem of this embodiment utilizes wireline protocols to add itself asan authorized control device in security system 1610.

A description of an example embodiment follows in which the Gateway(FIG. 16, element 1620) is the iHub available from iControl Networks,Palo Alto, Calif., and described in detail herein. In this example thegateway is “automatically” installed with a security system.

The automatic security system installation begins with the assignment ofan authorization key to components of the security system (e.g.,gateway, kit including the gateway, etc.). The assignment of anauthorization key is done in lieu of creating a user account. Aninstaller later places the gateway in a user's premises along with thepremises security system. The installer uses a computer to navigate to aweb portal (e.g., integrated security system web interface), logs in tothe portal, and enters the authorization key of the installed gatewayinto the web portal for authentication. Once authenticated, the gatewayautomatically discovers devices at the premises (e.g., sensors, cameras,light controls, etc.) and adds the discovered devices to the system or“network”. The installer assigns names to the devices, and testsoperation of the devices back to the server (e.g., did the door open,did the camera take a picture, etc.). The security device information isoptionally pushed or otherwise propagated to a security panel and/or tothe server network database. The installer finishes the installation,and instructs the end user on how to create an account, username, andpassword. At this time the user enters the authorization key whichvalidates the account creation (uses a valid authorization key toassociate the network with the user's account). New devices maysubsequently be added to the security network in a variety of ways(e.g., user first enters a unique ID for each device/sensor and names itin the server, after which the gateway can automatically discover andconfigure the device).

A description of another example embodiment follows in which thesecurity system (FIG. 16, element 1610) is a Dialog system and the WSP(FIG. 16, element 1611) is a SimonXT available from General ElectricSecurity, and the Gateway (FIG. 16, element 1620) is the iHub availablefrom iControl Networks, Palo Alto, Calif., and described in detailherein. Descriptions of the install process for the SimonXT and iHub arealso provided below.

GE Security's Dialog network is one of the most widely deployed andtested wireless security systems in the world. The physical RF networkis based on a 319.5 MHz unlicensed spectrum, with a bandwidth supportingup to 19 Kbps communications. Typical use of this bandwidth—even inconjunction with the integrated security system—is far less than that.Devices on this network can support either one-way communication (eithera transmitter or a receiver) or two-way communication (a transceiver).Certain GE Simon, Simon XT, and Concord security control panelsincorporate a two-way transceiver as a standard component. The gatewayalso incorporates the same two-way transceiver card. The physical linklayer of the network is managed by the transceiver module hardware andfirmware, while the coded payload bitstreams are made available to theapplication layer for processing.

Sensors in the Dialog network typically use a 60-bit protocol forcommunicating with the security panel transceiver, while security systemkeypads and the gateway use the encrypted 80-bit protocol. The Dialognetwork is configured for reliability, as well as low-power usage. Manydevices are supervised, i.e. they are regularly monitored by the system‘master’ (typically a GE security panel), while still maintainingexcellent power usage characteristics. A typical door window sensor hasa battery life in excess of 5-7 years.

The gateway has two modes of operation in the Dialog network: a firstmode of operation is when the gateway is configured or operates as a‘slave’ to the GE security panel; a second mode of operation is when thegateway is configured or operates as a ‘master’ to the system in theevent a security panel is not present. In both configurations, thegateway has the ability to ‘listen’ to network traffic, enabling thegateway to continually keep track of the status of all devices in thesystem. Similarly, in both situations the gateway can address andcontrol devices that support setting adjustments (such as the GEwireless thermostat).

In the configuration in which the gateway acts as a ‘slave’ to thesecurity panel, the gateway is ‘learned into’ the system as a GEwireless keypad. In this mode of operation, the gateway emulates asecurity system keypad when managing the security panel, and can querythe security panel for status and ‘listen’ to security panel events(such as alarm events).

The gateway incorporates an RF Transceiver manufactured by GE Security,but is not so limited. This transceiver implements the Dialog protocolsand handles all network message transmissions, receptions, and timing.As such, the physical, link, and protocol layers of the communicationsbetween the gateway and any GE device in the Dialog network are totallycompliant with GE Security specifications.

At the application level, the gateway emulates the behavior of a GEwireless keypad utilizing the GE Security 80-bit encrypted protocol, andonly supported protocols and network traffic are generated by thegateway. Extensions to the Dialog RF protocol of an embodiment enablefull control and configuration of the panel, and iControl can bothautomate installation and sensor enrollment as well as directconfiguration downloads for the panel under these protocol extensions.

As described above, the gateway participates in the GE Security networkat the customer premises. Because the gateway has intelligence and atwo-way transceiver, it can ‘hear’ all of the traffic on that network.The gateway makes use of the periodic sensor updates, state changes, andsupervisory signals of the network to maintain a current state of thepremises. This data is relayed to the integrated security system server(e.g., FIG. 2, element 260) and stored in the event repository for useby other server components. This usage of the GE Security RF network iscompletely non-invasive; there is no new data traffic created to supportthis activity.

The gateway can directly (or indirectly through the Simon XT panel)control two-way devices on the network. For example, the gateway candirect a GE Security Thermostat to change its setting to ‘Cool’ from‘Off’, as well as request an update on the current temperature of theroom. The gateway performs these functions using the existing GE Dialogprotocols, with little to no impact on the network; a gateway devicecontrol or data request takes only a few dozen bytes of data in anetwork that can support 19 Kbps.

By enrolling with the Simon XT as a wireless keypad, as describedherein, the gateway includes data or information of all alarm events, aswell as state changes relevant to the security panel. This informationis transferred to the gateway as encrypted packets in the same way thatthe information is transferred to all other wireless keypads on thenetwork.

Because of its status as an authorized keypad, the gateway can alsoinitiate the same panel commands that a keypad can initiate. Forexample, the gateway can arm or disarm the panel using the standardDialog protocol for this activity. Other than the monitoring of standardalarm events like other network keypads, the only incremental datatraffic on the network as a result of the gateway is the infrequentremote arm/disarm events that the gateway initiates, or infrequentqueries on the state of the panel.

The gateway is enrolled into the Simon XT panel as a ‘slave’ devicewhich, in an embodiment, is a wireless keypad. This enables the gatewayfor all necessary functionality for operating the Simon XT systemremotely, as well as combining the actions and information ofnon-security devices such as lighting or door locks with GE Securitydevices. The only resource taken up by the gateway in this scenario isone wireless zone (sensor ID).

The gateway of an embodiment supports three forms of sensor and panelenrollment/installation into the integrated security system, but is notlimited to this number of enrollment/installation options. Theenrollment/installation options of an embodiment include installerinstallation, kitting, and panel, each of which is described below.

Under the installer option, the installer enters the sensor IDs at timeof installation into the integrated security system web portal oriScreen. This technique is supported in all configurations andinstallations.

Kits can be pre-provisioned using integrated security systemprovisioning applications when using the kitting option. At kittingtime, multiple sensors are automatically associated with an account, andat install time there is no additional work required.

In the case where a panel is installed with sensors already enrolled(i.e. using the GE Simon XT enrollment process), the gateway has thecapability to automatically extract the sensor information from thesystem and incorporate it into the user account on the integratedsecurity system server.

The gateway and integrated security system of an embodiment uses anauto-learn process for sensor and panel enrollment in an embodiment. Thedeployment approach of an embodiment can use additional interfaces thatGE Security is adding to the Simon XT panel. With these interfaces, thegateway has the capability to remotely enroll sensors in the panelautomatically. The interfaces include, but are not limited to, thefollowing: EnrollDevice(ID, type, name, zone, group);SetDeviceParameters(ID, type, Name, zone, group),GetDeviceParameters(zone); and RemoveDevice(zone).

The integrated security system incorporates these new interfaces intothe system, providing the following install process. The install processcan include integrated security system logistics to handle kitting andpre-provisioning. Pre-kitting and logistics can include apre-provisioning kitting tool provided by integrated security systemthat enables a security system vendor or provider (“provider”) to offerpre-packaged initial ‘kits’. This is not required but is recommended forsimplifying the install process. This example assumes a ‘Basic’ kit ispreassembled and includes one (1) Simon XT, three (3) Door/windowsensors, one (1) motion sensor, one (1) gateway, one (1) keyfob, two (2)cameras, and ethernet cables. The kit also includes a sticker page withall Zones (1-24) and Names (full name list).

The provider uses the integrated security system kitting tool toassemble ‘Basic’ kit packages. The contents of different types ofstarter kits may be defined by the provider. At the distributionwarehouse, a worker uses a bar code scanner to scan each sensor and thegateway as it is packed into the box. An ID label is created that isattached to the box. The scanning process automatically associates allthe devices with one kit, and the new ID label is the unique identifierof the kit. These boxes are then sent to the provider for distributionto installer warehouses. Individual sensors, cameras, etc. are also sentto the provider installer warehouse. Each is labeled with its ownbarcode/ID.

An installation and enrollment procedure of a security system includinga gateway is described below as one example of the installation process.

-   1. Order and Physical Install Process    -   a. Once an order is generated in the iControl system, an account        is created and an install ticket is created and sent        electronically to the provider for assignment to an installer.    -   b. The assigned installer picks up his/her ticket(s) and fills        his/her truck with Basic and/or Advanced starter kits. He/she        also keeps a stock of individual sensors, cameras, iHubs, Simon        XTs, etc. Optionally, the installer can also stock homeplug        adapters for problematic installations.    -   c. The installer arrives at the address on the ticket, and pulls        out the Basic kit. The installer determines sensor locations        from a tour of the premises and discussion with the homeowner.        At this point assume the homeowner requests additional equipment        including an extra camera, two (2) additional door/window        sensors, one (1) glass break detector, and one (1) smoke        detector.    -   d. Installer mounts SimonXT in the kitchen or other location in        the home as directed by the homeowner, and routes the phone line        to Simon XT if available. GPRS and Phone numbers pre-programmed        in SimonXT to point to the provider Central Monitoring Station        (CMS).    -   e. Installer places gateway in the home in the vicinity of a        router and cable modem. Installer installs an ethernet line from        gateway to router and plugs gateway into an electrical outlet.-   2. Associate and Enroll gateway into SimonXT    -   a. Installer uses either his/her own laptop plugged into router,        or homeowners computer to go to the integrated security system        web interface and log in with installer ID/pass.    -   b. Installer enters ticket number into admin interface, and        clicks ‘New Install’ button. Screen prompts installer for kit ID        (on box's barcode label).    -   c. Installer clicks ‘Add SimonXT’. Instructions prompt installer        to put Simon XT into install mode, and add gateway as a wireless        keypad. It is noted that this step is for security only and can        be automated in an embodiment.    -   d. Installer enters the installer code into the Simon XT.        Installer Learns ‘gateway’ into the panel as a wireless keypad        as a group 1 device.    -   e. Installer goes back to Web portal, and clicks the ‘Finished        Adding SimonXT’ button.-   3. Enroll Sensors into SimonXT Via iControl    -   a. All devices in the Basic kit are already associated with the        user's account.    -   b. For additional devices, Installer clicks ‘Add Device’ and        adds the additional camera to the user's account (by typing in        the camera ID/Serial #).    -   c. Installer clicks ‘Add Device’ and adds other sensors (two (2)        door/window sensors, one (1) glass break sensor, and one (1)        smoke sensor) to the account (e.g., by typing in IDs).    -   d. As part of Add Device, Installer assigns zone, name, and        group to the sensor. Installer puts appropriate Zone and Name        sticker on the sensor temporarily.    -   e. All sensor information for the account is pushed or otherwise        propagated to the iConnect server, and is available to propagate        to CMS automation software through the CMS application        programming interface (API).    -   f. Web interface displays ‘Installing Sensors in System . . . .        ’ and automatically adds all of the sensors to the Simon XT        panel through the GE RF link.    -   g. Web interface displays ‘Done Installing’→all sensors show        green.-   4. Place and Tests Sensors in Home    -   a. Installer physically mounts each sensor in its desired        location, and removes the stickers.    -   b. Installer physically mounts WiFi cameras in their location        and plugs into AC power. Optional fishing of low voltage wire        through wall to remove dangling wires. Camera transformer is        still plugged into outlet but wire is now inside the wall.    -   c. Installer goes to Web interface and is prompted for automatic        camera install. Each camera is provisioned as a private,        encrypted Wifi device on the gateway secured sandbox network,        and firewall NAT traversal is initiated. Upon completion the        customer is prompted to test the security system.    -   d. Installer selects the ‘Test System’ button on the web        portal—the SimonXT is put into Test mode by the gateway over GE        RF.    -   e. Installer manually tests the operation of each sensor,        receiving an audible confirmation from SimonXT.    -   f. gateway sends test data directly to CMS over broadband link,        as well as storing the test data in the user's account for        subsequent report generation.    -   g. Installer exits test mode from the Web portal.-   5. Installer instructs customer on use of the Simon XT, and shows    customer how to log into the iControl web and mobile portals.    Customer creates a username/password at this time.-   6. Installer instructs customer how to change Simon XT user code    from the Web interface. Customer changes user code which is pushed    to SimonXT automatically over GE RF.

An installation and enrollment procedure of a security system includinga gateway is described below as an alternative example of theinstallation process. This installation process is for use for enrollingsensors into the SimonXT and integrated security system and iscompatible with all existing GE Simon panels.

The integrated security system supports all pre-kitting functionalitydescribed in the installation process above. However, for the purpose ofthe following example, no kitting is used.

-   -   1. Order and Physical Install Process        -   a. Once an order is generated in the iControl system, an            account is created and an install ticket is created and sent            electronically to the security system provider for            assignment to an installer.        -   b. The assigned installer picks up his/her ticket(s) and            fills his/her truck with individual sensors, cameras, iHubs,            Simon XTs, etc. Optionally, the installer can also stock            homeplug adapters for problematic installations.        -   c. The installer arrives at the address on the ticket, and            analyzes the house and talks with the homeowner to determine            sensor locations. At this point assume the homeowner            requests three (3) cameras, five (5) door/window sensors,            one (1) glass break detector, one (1) smoke detector, and            one (1) keyfob.        -   d. Installer mounts SimonXT in the kitchen or other location            in the home. The installer routes a phone line to Simon XT            if available. GPRS and Phone numbers are pre-programmed in            SimonXT to point to the provider CMS.        -   e. Installer places gateway in home in the vicinity of a            router and cable modem, and installs an ethernet line from            gateway to the router, and plugs gateway into an electrical            outlet.    -   2. Associate and Enroll gateway into SimonXT        -   a. Installer uses either his/her own laptop plugged into            router, or homeowners computer to go to the integrated            security system web interface and log in with an installer            ID/pass.        -   b. Installer enters ticket number into admin interface, and            clicks ‘New Install’ button. Screen prompts installer to add            devices.        -   c. Installer types in ID of gateway, and it is associated            with the user's account.        -   d. Installer clicks ‘Add Device’ and adds the cameras to the            user's account (by typing in the camera ID/Serial #).        -   e. Installer clicks ‘Add SimonXT’. Instructions prompt            installer to put Simon XT into install mode, and add gateway            as a wireless keypad.        -   f. Installer goes to Simon XT and enters the installer code            into the Simon XT. Learns ‘gateway’ into the panel as a            wireless keypad as group 1 type sensor.        -   g. Installer returns to Web portal, and clicks the ‘Finished            Adding SimonXT’ button.        -   h. Gateway now is alerted to all subsequent installs over            the security system RF.    -   3. Enroll Sensors into SimonXT via iControl        -   a. Installer clicks ‘Add Simon XT Sensors’—Displays            instructions for adding sensors to Simon XT.        -   b. Installer goes to Simon XT and uses Simon XT install            process to add each sensor, assigning zone, name, group.            These assignments are recorded for later use.        -   c. The gateway automatically detects each sensor addition            and adds the new sensor to the integrated security system.        -   d. Installer exits install mode on the Simon XT, and returns            to the Web portal.        -   e. Installer clicks ‘Done Adding Devices’.        -   f. Installer enters zone/sensor naming from recorded notes            into integrated security system to associate sensors to            friendly names.        -   g. All sensor information for the account is pushed to the            iConnect server, and is available to propagate to CMS            automation software through the CMS API.    -   4. Place and Tests Sensors in Home        -   a. Installer physically mounts each sensor in its desired            location.        -   b. Installer physically mounts Wifi cameras in their            location and plugs into AC power. Optional fishing of low            voltage wire through wall to remove dangling wires. Camera            transformer is still plugged into outlet but wire is now            inside the wall.        -   c. Installer puts SimonXT into Test mode from the keypad.        -   d. Installer manually tests the operation of each sensor,            receiving an audible confirmation from SimonXT.        -   e. Installer exits test mode from the Simon XT keypad.        -   f. Installer returns to web interface and is prompted to            automatically set up cameras. After waiting for completion            cameras are now provisioned and operational.    -   5. Installer instructs customer on use of the Simon XT, and        shows customer how to log into the integrated security system        web and mobile portals. Customer creates a username/password at        this time.    -   6. Customer and Installer observe that all sensors/cameras are        green.    -   7. Installer instructs customer how to change Simon XT user code        from the keypad. Customer changes user code and stores in        SimonXT.    -   8. The first time the customer uses the web portal to Arm/Disarm        system the web interface prompts the customer for the user code,        which is then stored securely on the server. In the event the        user code is changed on the panel the web interface once again        prompts the customer.

The panel of an embodiment can be programmed remotely. The CMS pushesnew programming to SimonXT over a telephone or GPRS link. Optionally,iControl and GE provide a broadband link or coupling to the gateway andthen a link from the gateway to the Simon XT over GE RF.

In addition to the configurations described above, the gateway of anembodiment supports takeover configurations in which it is introduced oradded into a legacy security system. A description of example takeoverconfigurations follow in which the security system (FIG. 2, element 210)is a Dialog system and the WSP (FIG. 2, element 211) is a GE Concordpanel (e.g., equipped with POTS, GE RF, and Superbus 2000 RS485interface (in the case of a Lynx takeover the Simon XT is used)available from General Electric Security. The gateway (FIG. 2, element220) in the takeover configurations is an iHub (e.g., equipped withbuilt-in 802.11b/g router, Ethernet Hub, GSM/GPRS card, RS485 inteface,and iControl Honeywell-compatible RF card) available from iControlNetworks, Palo Alto, Calif. While components of particular manufacturersare used in this example, the embodiments are not limited to thesecomponents or to components from these vendors.

The security system can optionally include RF wireless sensors (e.g., GEwireless sensors utilizing the GE Dialog RF technology), IP cameras, aGE-iControl Touchscreen (the touchscreen is assumed to be an optionalcomponent in the configurations described herein, and is thus treatedseparately from the iHub; in systems in which the touchscreen is acomponent of the base security package, the integrated iScreen(available from iControl Networks, Palo Alto, Calif.) can be used tocombine iHub technology with the touchscreen in a single unit), andZ-Wave devices to name a few.

The takeover configurations described below assume takeover by a “new”system of an embodiment of a security system provided by another thirdparty vendor, referred to herein as an “original” or “legacy” system.Generally, the takeover begins with removal of the control panel andkeypad of the legacy system. A GE Concord panel is installed to replacethe control panel of the legacy system along with an iHub with GPRSModem. The legacy system sensors are then connected or wired to theConcord panel, and a GE keypad or touchscreen is installed to replacethe control panel of the legacy system. The iHub includes the iControlRF card, which is compatible with the legacy system. The iHub finds andmanages the wireless sensors of the legacy system, and learns thesensors into the Concord by emulating the corresponding GE sensors. TheiHub effectively acts as a relay for legacy wireless sensors.

Once takeover is complete, the new security system provides ahomogeneous system that removes the compromises inherent in taking overor replacing a legacy system. For example, the new system provides amodern touchscreen that may include additional functionality, newservices, and supports integration of sensors from variousmanufacturers. Furthermore, lower support costs can be realized becausecall centers, installers, etc. are only required to support onearchitecture. Additionally, there is minimal install cost because onlythe panel is required to be replaced as a result of the configurationflexibility offered by the iHub.

The system takeover configurations described below include but are notlimited to a dedicated wireless configuration, a dedicated wirelessconfiguration that includes a touchscreen, and a fished Ethernetconfiguration. Each of these configurations is described in detailbelow.

FIG. 76 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel wirelessly coupled to an iHub,under an embodiment. All existing wired and RF sensors remain in place.The iHub is located near the Concord panel, and communicates with thepanel via the 802.11 link, but is not so limited. The iHub managescameras through a built-in 802.11 router. The iHub listens to theexisting RF HW sensors, and relays sensor information to the Concordpanel (emulating the equivalent GE sensor). The wired sensors of thelegacy system are connected to the wired zones on the control panel.

FIG. 77 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel wirelessly coupled to an iHub,and a GE-iControl Touchscreen, under an embodiment. All existing wiredand RF sensors remain in place. The iHub is located near the Concordpanel, and communicates with the panel via the 802.11 link, but is notso limited. The iHub manages cameras through a built-in 802.11 router.The iHub listens to the existing RF HW sensors, and relays sensorinformation to the Concord panel (emulating the equivalent GE sensor).The wired sensors of the legacy system are connected to the wired zoneson the control panel.

The GE-iControl Touchscreen can be used with either of an 802.11connection or Ethernet connection with the iHub. Because the takeoverinvolves a GE Concord panel (or Simon XT), the touchscreen is always anoption. No extra wiring is required for the touchscreen as it can usethe 4-wire set from the replaced keypad of the legacy system. Thisprovides power, battery backup (through Concord), and data link (RS485Superbus 2000) between Concord and touchscreen. The touchscreen receivesits broadband connectivity through the dedicated 802.11 link to theiHub.

FIG. 78 is a block diagram of a security system in which the legacypanel is replaced with a GE Concord panel connected to an iHub via anEthernet coupling, under an embodiment. All existing wired and RFsensors remain in place. The iHub is located near the Concord panel, andwired to the panel using a 4-wire SUperbus 2000 (RS485) interface, butis not so limited. The iHub manages cameras through a built-in 802.11router. The iHub listens to the existing RF HW sensors, and relayssensor information to the Concord panel (emulating the equivalent GEsensor). The wired sensors of the legacy system are connected to thewired zones on the control panel.

The takeover installation process is similar to the installation processdescribed above, except the control panel of the legacy system isreplaced; therefore, only the differences with the installationdescribed above are provided here. The takeover approach of anembodiment uses the existing RS485 control interfaces that GE Securityand iControl support with the iHub, touchscreen, and Concord panel. Withthese interfaces, the iHub is capable of automatically enrolling sensorsin the panel. The exception is the leverage of an iControl RF cardcompatible with legacy systems to ‘takeover’ existing RF sensors. Adescription of the takeover installation process follows.

During the installation process, the iHub uses an RF Takeover Card toautomatically extract all sensor IDs, zones, and names from the legacypanel. The installer removes connections at the legacy panel fromhardwired wired sensors and labels each with the zone. The installerpulls the legacy panel and replaces it with the GE Concord panel. Theinstaller also pulls the existing legacy keypad and replaces it witheither a GE keypad or a GE-iControl touchscreen. The installer connectslegacy hardwired sensors to appropriate wired zone (from labels) on theConcord. The installer connects the iHub to the local network andconnects the iHub RS485 interface to the Concord panel. The iHubautomatically ‘enrolls’ legacy RF sensors into the Concord panel as GEsensors (maps IDs), and pushes or otherwise propagates other informationgathered from HW panel (zone, name, group). The installer performs atest of all sensors back to CMS. In operation, the iHub relays legacysensor data to the Concord panel, emulating equivalent GE sensorbehavior and protocols.

The areas of the installation process particular to the legacy takeoverinclude how the iHub extracts sensor info from the legacy panel and howthe iHub automatically enrolls legacy RF sensors and populates Concordwith wired zone information. Each of these areas is described below.

In having the iHub extract sensor information from the legacy panel, theinstaller ‘enrolls’ iHub into the legacy panel as a wireless keypad (useinstall code and house ID-available from panel). The iHub legacy RFTakeover Card is a compatible legacy RF transceiver. The installer usesthe web portal to place iHub into ‘Takeover Mode’, and the web portalthe automatically instructs the iHub to begin extraction. The iHubqueries the panel over the RF link (to get all zone information for allsensors, wired and RF). The iHub then stores the legacy sensorinformation received during the queries on the iConnect server.

The iHub also automatically enrolls legacy RF sensors and populatesConcord with wired zone information. In so doing, the installer selects‘Enroll legacy Sensors into Concord’ (next step in ‘Takeover’ process onweb portal). The iHub automatically queries the iConnect server, anddownloads legacy sensor information previously extracted. The downloadedinformation includes an ID mapping from legacy ID to ‘spoofed’ GE ID.This mapping is stored on the server as part of the sensor information(e.g., the iConnect server knows that the sensor is a legacy sensoracting in GE mode). The iHub instructs Concord to go into install mode,and sends appropriate Superbus 2000 commands for sensor learning to thepanel. For each sensor, the ‘spoofed’ GE ID is loaded, and zone, name,and group are set based on information extracted from legacy panel. Uponcompletion, the iHub notifies the server, and the web portal is updatedto reflect next phase of Takeover (e.g., ‘Test Sensors’).

Sensors are tested in the same manner as described above. When a HWsensor is triggered, the signal is captured by the iHub legacy RFTakeover Card, translated to the equivalent GE RF sensor signal, andpushed to the panel as a sensor event on the SuperBus 2000 wires.

In support of remote programming of the panel, CMS pushes newprogramming to Concord over a phone line, or to the iConnect CMS/AlarmServer API, which in turn pushes the programming to the iHub. The iHubuses the Concord Superbus 2000 RS485 link to push the programming to theConcord panel.

FIG. 79 is a flow diagram for automatic takeover 2100 of a securitysystem, under an embodiment. Automatic takeover includes establishing2102 a wireless coupling between a takeover component running under aprocessor and a first controller of a security system installed at afirst location. The security system includes some number of securitysystem components coupled to the first controller. The automatictakeover includes automatically extracting 2104 security data of thesecurity system from the first controller via the takeover component.The automatic takeover includes automatically transferring 2106 thesecurity data to a second controller and controlling loading of thesecurity data into the second controller. The second controller iscoupled to the security system components and replaces the firstcontroller.

FIG. 80 is a flow diagram for automatic takeover 2200 of a securitysystem, under an alternative embodiment. Automatic takeover includesautomatically forming 2202 a security network at a first location byestablishing a wireless coupling between a security system and agateway. The gateway of an embodiment includes a takeover component. Thesecurity system of an embodiment includes security system components.The automatic takeover includes automatically extracting 2204 securitydata of the security system from a first controller of the securitysystem. The automatic takeover includes automatically transferring 2206the security data to a second controller. The second controller of anembodiment is coupled to the security system components and replaces thefirst controller.

Components of the gateway of the integrated security system describedherein control discovery, installation and configuration of both wiredand wireless IP devices (e.g., cameras, etc.) coupled or connected tothe system, as described herein with reference to FIGS. 1-4, as well asmanagement of video routing using a video routing module or engine. Thevideo routing engine initiates communication paths for the transfer ofvideo from a streaming source device to a requesting client device, anddelivers seamless video streams to the user via the communication pathsusing one or more of UPnP port-forwarding, relay server routing andSTUN/TURN peer-to-peer routing, each of which is described below.

By way of reference, conventional video cameras have the ability tostream digital video in a variety of formats and over a variety ofnetworks. Internet protocol (IP) video cameras, which include videocameras using an IP transport network (e.g., Ethernet, WiFi (IEEE 802.11standards), etc.) are prevalent and increasingly being utilized in homemonitoring and security system applications. With the proliferation ofthe internet, Ethernet and WiFi local area networks (LANs) and advancedwide area networks (WANs) that offer high bandwidth, low latencyconnections (broadband), as well as more advanced wireless WAN datanetworks (e.g. GPRS or CDMA 1×RTT), there increasingly exists thenetworking capability to extend traditional security systems to offerIP-based video. However, a fundamental reason for such IP video in asecurity system is to enable a user or security provider to monitor liveor otherwise streamed video from outside the host premises (and theassociated LAN).

The conventional solution to this problem has involved a technique knownas ‘port fowarding’, whereby a ‘port’ on the LAN's router/firewall isassigned to the specific LAN IP address for an IP camera, or a proxy tothat camera. Once a port has been ‘forwarded’ in this manner, a computerexternal to the LAN can address the LAN's router directly, and requestaccess to that port. This access request is then forwarded by the routerdirectly to the IP address specified, the IP camera or proxy. In thisway an external device can directly access an IP camera within the LANand view or control the streamed video.

The issues with this conventional approach include the following: portforwarding is highly technical and most users do not know how/why to doit; automatic port forwarding is difficult and problematic usingemerging standards like UPnP; the camera IP address is often reset inresponse to a power outage/router reboot event; there are many differentrouters with different ways/capabilities for port forwarding. In short,although port forwarding can work, it is frequently less than adequateto support a broadly deployed security solution utilizing IP cameras.

Another approach to accessing streaming video externally to a LANutilizes peer-to-peer networking technology. So-called peer-to-peernetworks, which includes networks in which a device or client isconnected directly to another device or client, typically over a WideArea Network (WAN) and without a persistent server connection, areincreasingly common. In addition to being used for the sharing of filesbetween computers (e.g., Napster and KaZaa), peer-to-peer networks havealso been more recently utilized to facilitate direct audio and mediastreaming in applications such as Skype. In these cases, thepeer-to-peer communications have been utilized to enable telephony-stylevoice communications and video conferencing between two computers, eachenabled with an IP-based microphone, speaker, and video camera. Afundamental reason for adopting such peer-to-peer technology is theability to transparently ‘punch through’ LAN firewalls to enableexternal access to the streaming voice and video content, and to do soin a way that scales to tens of millions of users without creating anuntenable server load.

A limitation of the conventional peer-to-peer video transport lies inthe personal computer (PC)-centric nature of the solution. Each of theconventional solutions uses a highly capable PC connected to the videocamera, with the PC providing the advanced software functionalityrequired to initiate and manage the peer-to-peer connection with theremote client. A typical security or remote home monitoring systemrequires multiple cameras, each with its own unique IP address, and onlya limited amount of processing capability in each camera such that theconventional PC-centric approach cannot easily solve the need. Insteadof a typical PC-centric architecture with three components (a “3-way IPVideo System”) that include a computer device with video camera, amediating server, and a PC client with video display capability, theconventional security system adds a plurality of fourth components thatare standalone IP video cameras (requiring a “4-way IP Video System”),another less-than-ideal solution.

In accordance with the embodiments described herein, IP cameramanagement systems and methods are provided that enable a consumer orsecurity provider to easily and automatically configure and manage IPcameras located at a customer premise. Using this system IP cameramanagement may be extended to remote control and monitoring from outsidethe firewall and router of the customer premise.

With reference to FIGS. 5 and 6, the system includes a gateway 253having a video routing component so that the gateway 253 can manage andcontrol, or assist in management and control, or video routing. Thesystem also includes one or more cameras (e.g., WiFi IP camera 254,Ethernet IP camera 255, etc.) that communicate over the LAN 250 using anIP format, as well as a connection management server 210 located outsidethe premise firewall 252 and connected to the gateway 253 by a Wide AreaNetwork (WAN) 200. The system further includes one or more devices 220,230, 240 located outside the premise and behind other firewalls 221,231, 241 and connected to the WAN 200. The other devices 220, 230, 240are configured to access video or audio content from the IP cameraswithin the premise, as described above.

Alternatively, with reference to FIGS. 9 and 10, the system includes atouchscreen 902 or 1002 having a video routing component so that thetouchscreen 902 or 1002 can manage and control, or assist in managementand control, or video routing. The system also includes one or morecameras (e.g., WiFi IP camera 254, Ethernet IP camera 255, etc.) thatcommunicate over the LAN 250 using an IP format, as well as a connectionmanagement server 210 located outside the premise firewall 252 andconnected to the gateway 253 by a Wide Area Network (WAN) 200. Thesystem further includes one or more devices 220, 230, 240 locatedoutside the premise and behind other firewalls 221, 231, 241 andconnected to the WAN 200. The other devices 220, 230, 240 are configuredto access video or audio content from the IP cameras within the premise,as described above.

FIG. 81 is a general flow diagram for IP video control, under anembodiment. The IP video control interfaces, manages, and providesWAN-based remote access to a plurality of IP cameras in conjunction witha home security or remote home monitoring system. The IP video controlallows for monitoring and controlling of IP video cameras from alocation remote to the customer premise, outside the customer premisefirewall, and protected by another firewall. Operations begin when thesystem is powered on 2310, involving at a minimum the power-on of thegateway, as well as the power-on of at least one IP camera coupled orconnected to the premise LAN. The gateway searches 2311 for available IPcameras and associated IP addresses. The gateway selects 2312 from oneor more possible approaches to create connections between the IP cameraand a device external to the firewall. Once an appropriate connectionpath is selected, the gateway begins operation 2313, and awaits 2320 arequest for a stream from one of the plurality of IP video camerasavailable on the LAN. When a stream request is present the serverretrieves 2321 the requestor's WAN IP address/port.

When a server relay is present 2330, the IP camera is instructed 2331 tostream to the server, and the connection is managed 2332 through theserver. In response to the stream terminating 2351, operations return togateway operation 2313, and waits to receive another request 2320 for astream from one of the plurality of IP video cameras available on theLAN.

When a server relay is not present 2330, the requestor's WAN IPaddress/port is provided 2333 to the gateway or gateway relay. When agateway relay is present 2340, the IP camera is instructed 2341 tostream to the gateway, and the gateway relays 2342 the connection to therequestor. In response to the stream terminating 2351, operations returnto gateway operation 2313, and waits to receive another request 2320 fora stream from one of the plurality of IP video cameras available on theLAN. When a gateway relay is not present 2340, the IP camera isinstructed 2343 to stream to an address, and a handoff 2344 is maderesulting in direct communication between the camera and the requestor.In response to the stream terminating 2351, operations return to gatewayoperation 2313, and waits to receive another request 2320 from one ofthe plurality of IP video cameras available on the LAN.

The integrated security system of an embodiment supports numerous videostream formats or types of video streams. Supported video streamsinclude, but are not limited to, Motion Picture Experts Group (MPEG)-4(MPEG-4)/Real-Time Streaming Protocol (RTSP), MPEG-4 over HypertextTransfer Protocol (HTTP), and Motion Joint Photographic Experts Group(JPEG) (MJPEG).

The integrated security system of an embodiment supports the MPEG-4/RTSPvideo streaming method (supported by video servers and clients) whichuses RTSP for the control channel and Real-time Transport Protocol (RTP)for the data channel. Here the RTSP channel is over Transmission ControlProtocol (TCP) while the data channel uses User Datagram Protocol (UDP).This method is widely supported by both streaming sources (e.g.,cameras) and stream clients (e.g., remote client devices, AppleQuicktime, VideoLAN, IPTV mobile phones, etc).

Encryption can be added to the two channels under MPEG-4/RTSP. Forexample, the RTSP control channel can be encrypted using SSL/TLS. Thedata channel can also be encrypted.

If the camera or video stream source inside the home does not supportencryption for either RTSP or RTP channels, the gateway located on theLAN can facilitate the encrypted RTSP method by maintaining separate TCPsessions with the video stream source device and with the encrypted RTSPclient outside the LAN, and relay all communication between the twosessions. In this situation, any communication between the gateway andthe video stream source that is not encrypted could be encrypted by thegateway before being relayed to the RTSP client outside the LAN. In manycases the gateway is an access point for the encrypted and private Wifinetwork on which the video stream source device is located. This meansthat communication between the gateway and the video stream sourcedevice is encrypted at the network level, and communication between thegateway and the RTSP client is encrypted at the transport level. In thisfashion the gateway can compensate for a device that does not supportencrypted RTSP.

The integrated security system of an embodiment also supports reverseRTSP. Reverse RTSP includes taking a TCP-based protocol like RTSP, andreversing the roles of client and server (references to “server” includethe iControl server, also referred to as the iConnect server) when itcomes to TCP session establishment. For example, in standard RTSP theRTSP client is the one that establishes the TCP connection with thestream source server (the server listens on a port for incomingconnections). In Reverse RTSP, the RTSP client listens on a port forincoming connections from the stream source server. Once the TCPconnection is established, the RTSP client begins sending commands tothe server over the TCP connection just as it would in standard RTSP.

When using Reverse RTSP, the video stream source is generally on a LAN,protected by a firewall. Having a device on the LAN initiate theconnection to the RTSP client outside the firewall enables easy networktraversal.

If the camera or video stream source inside the LAN does not supportReverse RTSP, then the gateway facilitates the Reverse RTSP method byinitiating separate TCP sessions with the video stream source device andwith the Reverse RTSP client outside the LAN, and then relays allcommunication between the two sessions. In this fashion the gatewaycompensates for a stream source device that does not support ReverseRTSP.

As described in the encryption description above, the gateway canfurther compensate for missing functionalities on the device such asencryption. If the device does not support encryption for either RTSP orRTP channels, the gateway can communicate with the device using theseun-encrypted streams, and then encrypt the streams before relaying themout of the LAN to the RTSP Reverse client.

Servers of the integrated security system can compensate for RTSPclients that do not support Reverse RTSP. In this situation, the serveraccepts TCP connections from both the RTSP client and the Reverse RTSPvideo stream source (which could be a gateway acting on behalf of astream source device that does not support Reverse RTSP). The serverthen relays the control and video streams from the Reverse RTSP videostream source to the RTSP client. The server can further compensate forthe encryption capabilities of the RTSP client; if the RTSP client doesnot support encryption then the server can provide an unencrypted streamto the RTSP client even though an encrypted stream was received from theReverse RTSP streaming video source.

The integrated security system of an embodiment also supports SimpleTraversal of User Datagram Protocol (UDP) through Network AddressTranslators (NAT) (STUN)/Traversal Using Relay NAT (TURN) peer-to-peerrouting. STUN and Turn are techniques for using a server to helpestablish a peer-to-peer UDP data stream (it does not apply to TCPstreams). The bandwidth consumed by the data channel of a video streamis usually many thousands of times larger than that used by the controlchannel. Consequently, when a peer-to-peer connection for both the RTSPand RTP channels is not possible, there is still a great incentive touse STUN/TURN techniques in order to achieve a peer-to-peer connectionfor the RTP data channel.

Here, a method referred to herein as RTSP with STUN/TURN is used by theintegrated security system. The RTSP with STUN/TURN is a method in whichthe video streaming device is instructed over the control channel tostream its UDP data channel to a different network address than that ofthe other end of the control TCP connection (usually the UDP data issimply streamed to the IP address of the RTSP client). The result isthat the RTSP or Reverse RTSP TCP channel can be relayed using thegateway and/or the server, while the RTP UDP data channel can flowdirectly from the video stream source device to the video stream client.

If a video stream source device does not support RTSP with STUN/TURN,the gateway can compensate for the device by relaying the RTSP controlchannel via the server to the RTSP client, and receiving the RTP datachannel and then forwarding it directly to the RTSP with STUN/TURNenabled client. Encryption can also be added here by the gateway.

The integrated security system of an embodiment supports MPEG-4 overHTTP. MPEG-4 over HTTP is similar to MPEG-4 over RTSP except that boththe RTSP control channel and the RTP data channel are passed over anHTTP TCP session. Here a single TCP session can be used, splitting itinto multiple channels using common HTTP techniques like chunkedtransfer encoding.

The MPEG-4 over HTTP is generally supported by many video stream clientsand server devices, and encryption can easily be added to it usingSSL/TLS. Because it uses TCP for both channels, STUN/TURN techniques maynot apply in the event that a direct peer-to-peer TCP session betweenclient and server cannot be established.

As described above, encryption can be provided using SSL/TLS taking theform of HTTPS. And as with MPEG-4 over RTSP, a gateway can compensatefor a stream source device that does not support encryption by relayingthe TCP streams and encrypting the TCP stream between the gateway andthe stream client. In many cases the gateway is an access point for theencrypted and private Wifi network on which the video stream sourcedevice is located. This means that communication between the gateway andthe video stream source device is encrypted at the network level, andcommunication between the gateway and the video stream client isencrypted at the transport level. In this fashion the gateway cancompensate for a device that does not support HTTPS.

As with Reverse RTSP, the integrated security system of an embodimentsupports Reverse HTTP. Reverse HTTP includes taking a TCP-based protocollike HTTP, and reversing the roles of client and server when it comes toTCP session establishment. For example, in conventional HTTP the HTTPclient is the one that establishes the TCP connection with the server(the server listens on a port for incoming connections). In ReverseHTTP, the HTTP client listens on a port for incoming connections fromthe server. Once the TCP connection is established, the HTTP clientbegins sending commands to the server over the TCP connection just as itwould in standard HTTP.

When using Reverse HTTP, the video stream source is generally on a LAN,protected by a firewall. Having a device on the LAN initiate theconnection to the HTTP client outside the firewall enables easy networktraversal.

If the camera or video stream source inside the LAN does not supportReverse HTTP, then the gateway can facilitate the Reverse HTTP method byinitiating separate TCP sessions with the video stream source device andwith the Reverse HTTP client outside the LAN, and then relay allcommunication between the two sessions. In this fashion the gateway cancompensate for a stream source device that does not support ReverseHTTP.

As described in the encryption description above, the gateway canfurther compensate for missing functionalities on the device such asencryption. If the device does not support encrypted HTTP (e.g., HTTPS),then the gateway can communicate with the device using HTTP, and thenencrypt the TCP stream(s) before relaying out of the LAN to the ReverseHTTP client.

The servers of an embodiment can compensate for HTTP clients that do notsupport Reverse HTTP. In this situation, the server accepts TCPconnections from both the HTTP client and the Reverse HTTP video streamsource (which could be a gateway acting on behalf of a stream sourcedevice that does not support Reverse HTTP). The server then relays theTCP streams from the Reverse HTTP video stream source to the HTTPclient. The server can further compensate for the encryptioncapabilities of the HTTP client; if the HTTP client does not supportencryption then the server can provide an unencrypted stream to the HTTPclient even though an encrypted stream was received from the ReverseHTTP streaming video source.

The integrated security system of an embodiment supports MJPEG asdescribed above. MJPEG is a streaming technique in which a series of JPGimages are sent as the result of an HTTP request. Because MJPEG streamsare transmitted over HTTP, HTTPS can be employed for encryption and mostMJPEG clients support the resulting encrypted stream. And as with MPEG-4over HTTP, a gateway can compensate for a stream source device that doesnot support encryption by relaying the TCP streams and encrypting theTCP stream between the gateway and the stream client. In many cases thegateway is an access point for the encrypted and private Wifi network onwhich the video stream source device is located. This means thatcommunication between the gateway and the video stream source device isencrypted at the network level, and communication between the gatewayand the video stream client is encrypted at the transport level. In thisfashion the gateway can compensate for a device that does not supportHTTPS.

The integrated system of an embodiment supports Reverse HTTP. ReverseHTTP includes taking a TCP-based protocol like HTTP, and reversal of theroles of client and server when it comes to TCP session establishmentcan be employed for MJPEG streams. For example, in standard HTTP theHTTP client is the one who establishes the TCP connection with theserver (the server listens on a port for incoming connections). InReverse HTTP, the HTTP client listens on a port for incoming connectionsfrom the server. Once the TCP connection is established, the HTTP clientbegins sending commands to the server over the TCP connection just as itwould in standard HTTP.

When using Reverse HTTP, the video stream source is generally on a LAN,protected by a firewall. Having a device on the LAN initiate theconnection to the HTTP client outside the firewall enables networktraversal.

If the camera or video stream source inside the LAN does not supportReverse HTTP, then the gateway can facilitate the Reverse HTTP method byinitiating separate TCP sessions with the video stream source device andwith the Reverse HTTP client outside the LAN, and then relay allcommunication between the two sessions. In this fashion the gateway cancompensate for a stream source device that does not support ReverseHTTP.

As described in the encryption description above, the gateway canfurther compensate for missing functionalities on the device such asencryption. If the device does not support encrypted HTTP (e.g., HTTPS),then the gateway can communicate with the device using HTTP, and thenencrypt the TCP stream(s) before relaying out of the LAN to the ReverseHTTP client.

The servers can compensate for HTTP clients that do not support ReverseHTTP. In this situation, the server accepts TCP connections from boththe HTTP client and the Reverse HTTP video stream source (which could bea gateway acting on behalf of a stream source device that does notsupport Reverse HTTP). The server then relays the TCP streams from theReverse HTTP video stream source to the HTTP client. The server canfurther compensate for the encryption capabilities of the HTTP client;if the HTTP client does not support encryption then the server canprovide an unencrypted stream to the HTTP client even though anencrypted stream was received from the Reverse HTTP streaming videosource.

The integrated security system of an embodiment considers numerousparameters in determining or selecting one of the streaming formatsdescribed above for use in transferring video streams. The parametersconsidered in selecting a streaming format include, but are not limitedto, security requirements, client capabilities, device capabilities, andnetwork/system capabilities.

The security requirements for a video stream are considered indetermining an applicable streaming format in an embodiment. Securityrequirements fall into two categories, authentication and privacy, eachof which is described below.

Authentication as a security requirement means that stream clients mustpresent credentials in order to obtain a stream. Furthermore, thispresentation of credentials should be done in a way that is secure fromnetwork snooping and replays. An example of secure authentication isBasic Authentication over HTTPS. Here a username and password arepresented over an encrypted HTTPS channel so snooping and replays areprevented. Basic Authentication alone, however, is generally notsufficient for secure authentication.

Because not all streaming clients support SSL/TLS, authenticationmethods that do not require it are desirable. Such methods includeDigest Authentication and one-time requests. A one-time request is arequest that can only be made by a client one time, and the serverprevents a reuse of the same request. One-time requests are used tocontrol access to a stream source device by stream clients that do notsupport SSL/TLS. An example here is providing video access to a mobilephone. Typical mobile phone MPEG-4 viewers do not support encryption. Inthis case, one of the MPEG-4 over RTSP methods described above can beemployed to get the video stream relayed to an server. The server canthen provide the mobile phone with a one-time request Universal ResourceLocator (URL) for the relayed video stream source (via a WirelessApplication Protocol (WAP) page). Once the stream ends, the mobile phonewould need to obtain another one-time request URL from the server (viaWAP, for example) in order to view the stream again.

Privacy as a security requirement means that the contents of the videostream must be encrypted. This is a requirement that may be impossibleto satisfy on clients that do not support video stream encryption, forexample many mobile phones. If a client supports encryption for somevideo stream format(s), then the “best” of those formats should beselected. Here “best” is determined by the stream type priorityalgorithm.

The client capabilities are considered in determining an applicablestreaming format in an embodiment. In considering client capabilities,the selection depends upon the supported video stream formats thatinclude encryption, and the supported video stream formats that do notsupport encryption.

The device capabilities are considered in determining an applicablestreaming format in an embodiment. In considering device capabilities,the selection depends upon the supported video stream formats thatinclude encryption, the supported video stream formats that do notsupport encryption, and whether the device is on an encrypted privateWifi network managed by the gateway (in which case encryption at thenetwork level is not required).

The network/system capabilities are considered in determining anapplicable streaming format in an embodiment. In consideringnetwork/system capabilities, the selection depends upon characteristicsof the network or system across which the stream must travel. Thecharacteristics considered include, for example, the following: whetherthere is a gateway and/or server on the network to facilitate some ofthe fancier video streaming types or security requirements; whether theclient is on the same LAN as the gateway, meaning that network firewalltraversal is not needed.

Streaming methods with the highest priority are peer-to-peer becausethey scale best with server resources. Universal Plug and Play (UPnP)can be used by the gateway to open ports on the video stream device'sLAN router and direct traffic through those ports to the video streamdevice. This allows a video stream client to talk directly with thevideo stream device or talk directly with the gateway which can in turnfacilitate communication with the video stream device.

Another factor in determining the best video stream format to use is thesuccess of STUN and TURN methods for establishing direct peer-to-peerUDP communication between the stream source device and the streamclient. Again, the gateway and the server can help with the setup ofthis communication.

Client bandwidth availability and processing power are other factors indetermining the best streaming methods. For example, due to itsbandwidth overhead an encrypted MJPEG stream should not be consideredfor most mobile phone data networks.

Device bandwidth availability can also be considered in choosing thebest video stream format. For example, consideration can be given towhether the upstream bandwidth capabilities of the typical residentialDSL support two or more simultaneous MJPEG streams.

Components of the integrated security system of an embodiment, whileconsidering various parameters in selecting a video streaming format totransfer video streams from streaming source devices and requestingclient devices, prioritize streaming formats according to theseparameters. The parameters considered in selecting a streaming formatinclude, as described above, security requirements, client capabilities,device capabilities, and network/system capabilities. Components of theintegrated security system of an embodiment select a video streamingformat according to the following priority, but alternative embodimentscan use other priorities.

The selected format is UPnP or peer-to-peer MPEG-4 over RTSP withencryption when both requesting client device and streaming sourcedevice support this format.

The selected format is UPnP or peer-to-peer MPEG-4, over RTSP withauthentication when the requesting client device does not supportencryption or UPnP or peer-to-peer MPEG-4 over RTSP with encryption.

The selected format is UPnP (peer-to-peer) MPEG-4 over HTTPS when bothrequesting client device and streaming source device support thisformat.

The selected format is UPnP (peer-to-peer) MPEG-4 over HTTP when therequesting client device does not support encryption or UPnP(peer-to-peer) MPEG-4 over HTTPS.

The selected format is UPnP (peer-to-peer) MPEG-4 over RTSP facilitatedby gateway or touchscreen (including or incorporating gatewaycomponents) (to provide encryption), when the requesting client devicesupports encrypted RTSP and the streaming source device supports MPEG-4over RTSP.

The selected format is UPnP (peer-to-peer) MPEG-4 over HTTPS facilitatedby gateway or touchscreen (including or incorporating gatewaycomponents) (to provide encryption) when the requesting client devicesupports MPEG-4 over HTTPS and the streaming source device supportsMPEG-4 over HTTP.

The selected format is UPnP (peer-to-peer) MJPEG over HTTPS when thenetworks and devices can handle the bandwidth and both requesting clientdevice and streaming source device support MJPEG over HTTPS.

The selected format is Reverse RTSP with STUN/TURN facilitated by theserver when the streaming source device initiates SSL/TLS TCP to server,the streaming source device supports Reverse RTSP over SSL/TLS withSTUN/TURN, and the requesting client device supports RTSP withSTUN/TURN.

The selected format is Reverse RTSP with STUN/TURN facilitated by serverand gateway or touchscreen (including or incorporating gatewaycomponents) when the gateway initiates SSL/TLS TCP to the server and tothe streaming source device, the streaming source device supports RTSP,and the requesting client device supports RTSP with STUN/TURN.

The selected format is Reverse MPEG over RTSP/HTTP facilitated by theserver when the streaming source device initiates SSL/TLS TCP to server,the streaming source device supports Reverse RTSP or HTTP over SSL/TLS,and the requesting client device supports MPEG over RTSP/HTTP.

The selected format is Reverse MPEG over RTSP/HTTP facilitated by serverand gateway or touchscreen (including or incorporating gatewaycomponents) when the gateway initiates SSL/TLS TCP to server and tostreaming source device, the streaming source device supports MPEG overRTSP or HTTP, and the requesting client device supports MPEG overRTSP/HTTP.

The selected format is UPnP (peer-to-peer) MJPEG over HTTP when thenetworks and devices can handle the bandwidth and when the requestingclient device does not support encryption and does not support MPEG-4.

The selected format is Reverse MJPEG over HTTPS facilitated by theserver when the streaming source device initiates SSL/TLS TCP to server,the streaming source device supports Reverse MJPEG over SSL/TLS, and therequesting client device supports MJPEG.

The selected format is Reverse MJPEG over HTTPS facilitated by serverand gateway or touchscreen (including or incorporating gatewaycomponents) when the gateway initiates SSL/TLS TCP to the server and tothe streaming source device, the streaming source device supports MJPEG,and the requesting client device supports MJPEG.

FIG. 82 is a block diagram showing camera tunneling, under anembodiment.

Additional detailed description of camera tunnel implementation detailsfollow.

An embodiment uses XMPP for communication with a remote video camera asa lightweight (bandwidth) method for maintaining real-time communicationwith the remote camera. More specifically, the remote camera is locatedon another NAT (e.g., NAT traversal).

An embodiment comprises a method for including a remotely located camerain a home automation system. For example, using XMPP via cloud XMPPserver to couple or connect camera to home automation system. This canbe used with in-car cameras, cell phone cameras, and re-locatablecameras (e.g., dropped in the office, the hotel room, the neighbor'shouse, etc.).

Components of an embodiment are distributed so that any one can beoffline while system continues to function (e.g., panel can be downwhile camera still up, motion detection from camera, video clip uploadetc. continue to work.

Embodiments extend the PSIA in one or more of the following areas: wifiroaming configuration; video relay commands; wifi connectivity test;media tunnel for live video streaming in the context of a securitysystem; motion notification mechanism and configuration (motionheartbeat) (e.g., helps with scalable server); XMPP for lightweightcommunication (helps with scalable server, reduced bandwidth, formaintaining persistent connection with a gateway); ping request sentover XMPP as health check mechanism; shared secret authenticationbootstrapping process; asynchronous error status delivery by the camerafor commands invoked by the gateway if the camera is responsible fordelivering errors to the gateway in an asynchronous fashion (e.g.,gateway requests a firmware update or a video clip upload).

Embodiments extend the home automation system to devices located onseparate networks, and make them useable as general-purposecommunication devices. These cameras can be placed in the office,vacation home, neighbor house, software can be put onto a cell phone,into a car, navigation system, etc.

Embodiments use a global device registry for enabling a device/camera tolocate the server and home to which it is assigned.

Embodiments include methods for bootstrapping and re-bootstrapping ofauthentication credentials. The methods include activation key entry byinstaller into the cloud web interface. Activation key generation isbased upon mac address and a shared secret between manufacturer and theservice provider. Embodiments of the system allow activation of a camerawith valid activation key that is not already provisioned in the globalregistry server.

Embodiments include a web-based interface for use in activating,configuring, remote firmware update, and re-configuring of a camera.

Embodiments process or locate local wifi access points and provide theseas options during camera configuring and re-configuring. Embodimentsgenerate and provide recommendations around choosing a best wifi accesspoint based upon characteristics of the network (e.g., signal strength,error rates, interference, etc.). Embodiments include methods fortesting and diagnosing issues with wifi and network access.

Embodiments include cameras able to perform this wifi test using onlyone physical network interface, an approach that enables the camera todynamically change this physical interface from wired to wifi.Embodiments are able to change the network settings (wifi etc) remotelyusing the same process.

Cameras of an embodiment can be configured with multiple networkpreferences with priority order so that the camera can move betweendifferent locations and the camera can automatically find the bestnetwork to join (e.g., can have multiple ssid+bssid+password setsconfigured and prioritized).

Regarding firmware download, embodiments include a mechanism to monitorthe status of the firmware update, provide feedback to the end user andimprove overall quality of the system.

Embodiments use RTSP over SSL to a cloud media relay server to allowlive video NAT traversal to a remote client (e.g., PC, cell phone, etc.)in a secure manner where the camera provides media sessionauthentication credentials to the server. The camera initiates the SSLconnection to the cloud and then acts as a RTSP server over thisconnection.

Embodiments include methods for using NAT traversal for connecting tothe cloud for remote management and live video access allows theintegrated security components to avoid port forwarding on the localrouter(s) and as a result maintain a more secure local network and amore secure camera since no ports are required to be open.

Embodiments enable camera sensors (e.g., motion, audio, heat, etc.) toserve as triggers to other actions in the automation system. The captureof video clips or snapshots from the camera is one such action, but theembodiments are not so limited.

A camera of an embodiment can be used by multiple systems.

A detailed description of flows follows relating to the camera tunnel ofan embodiment.

A detailed description of camera startup and installation follows as itpertains to the camera tunnel of an embodiment.

Activation Key

-   -   a. camera to follow same algorithm as ihub where activation key        is generated from serial based upon a one-way hash on serial and        a per-vendor shared secret.    -   b. Used com.icontrol.util.ops.activation.ActivationKeyUtil class        to validate serialNo <-> activationKey.        Registry Request        [partner]/registry/[device type]/[serial]    -   a. new column in existing registry table for id type; nullable        but the application treats null as “gateway”.    -   b. rest endpoints allow adding with the new optional argument.    -   c. current serial and siteId uniqueness enforcement by        application depends upon device type (for any device type, there        should be uniqueness on serial; for gateway device type, there        should be uniqueness on siteId; for other device types, there        need not be uniqueness on siteId).    -   d. if no activation yet (e.g., no entry) then send dummy        response (random but repeatable reply; may include predictable        “dummy” so that steps below can infer.    -   e. add/update registry server endpoints for adding/updating        entries.        If Camera has No Password        Camera retrieves “Pending Key” via POST to        /<CredentialGatewayURL>/GatewayService/<siteID>/PendingDeviceKey.    -   a. pending key request (to get password) with serial and        activation key.    -   b. server checks for dummy reply; if dummy then responds with        retry backoff response.    -   c. server invokes pass-through API on gateway to get new pending        key.    -   d. if device is found, then gateway performs validation of        serial+activation key, returns error if mismatch.    -   e. if activation key checks out, then gateway checks pending key        status.    -   f. if device currently has a pending key status, then a new        pending password is generated.    -   g. gateway maintains this authorization information in a new set        of variables on the camera device.    -   h. device-authorization/session-key comprises the current        connected password.    -   i. device-authorization/pending-expiry comprises a UTC timestamp        representing the time the current pending password period ends;        any value less than the current time or blank means the device        is not in a pending password state.    -   j. device-authorization/pending-session-key comprises the last        password returned to the camera in a pending request; this is        optional (device may choose to maintain this value in memory).    -   k. session-key and pending-session-key variables tagged with        “encryption” in the device def which causes rest and admin to        hide their value from client.        ConnectInfo Request    -   a. returns xmpp host and port to connect to (comes from config        as it does for gateway connect info).    -   b. returns connectInfo with additional <xmpp> parameter.        Start Portal Add Camera Wizard    -   a. user enters camera serial, activation key.    -   b. addDevice rest endpoint on gateway called    -   c. gateway verifies activation key is correct.    -   d. gateway calls addDevice method on gapp server to add        LWG_SerComm_iCamera_1000 with given serial to site.    -   e. Server detects the camera type and populates registry.    -   f. gateway puts device into pending password state (e.g.,        updates device-auth/pending-expiry point).    -   g. rest endpoints on gateway device for managing device pending        password state.    -   h. start pending password state: POST future UTC value to        device-auth/pending-expiry; device-auth/pending-expiry set to 30        minutes from time device was added.    -   i. stop pending password state: POST −1 to        device-auth/pending-expiry.    -   j. check pending password state: GET device-auth/pending-expiry.    -   k. message returned with “Location” header pointing to relative        URI.    -   l. user told to power on camera (or reboot if already powered        on).    -   m. once camera connects, gateway updates        device-auth/pending-expiry to −1 and device-auth/session-key        with password and device/connection-status to connected    -   n. portal polls for device/connection-status to change to        connected; if does not connect after X seconds, bring up error        page (camera has not connected—continue waiting or start over).    -   o. user asked if wifi should be configured for this camera.    -   p. entry fields for wifi ssid and password.    -   q. portal can pre-populate ssid and password fields with        picklist of any from other cameras on the site.    -   r. get XML of available SSIDs.    -   s. non-wifi option is allowed.    -   t. portal submits options to configure camera (use null values        to specify non-wifi); upon success, message is returned with        “Location” header pointing to relative URI.    -   u. checks configuration progress and extracting “status” and        “subState” fields.    -   v. puts device state into “configuring”; upon error, puts device        state into “configuration failure”.    -   w. performs firmware upgrade if needed, placing device state        into “upgrading”; upon error, puts device state into “upgrade        failure”.    -   x. upon configuration success, puts device state of “ok” and        applies appropriate configuration for camera (e.g., resolutions,        users, etc.).    -   y. if non-blank wifi parameters, automatically perform “wifi        test” method to test wifi without disconnecting Ethernet.    -   z. portal wizard polls device status until changes to “ok” or        “upgrade failure/“configuration failure” in “status” field,        along with applicable, if any, with error code reason, in        “subState” field; upon error, show details to user, provide        options (start over, configure again, reboot, factory reset,        etc)    -   aa. notify user they can move camera to desired location.        Camera reboots    -   a. gets siteId and server URL from registry.    -   b. makes pending paid key request to server specifying correct        siteId, serial and activation key; gets back pending password.    -   c. makes connectInfo request to get xmpp server.    -   d. connects over xmpp with pending password.        If Camera Reboots Again    -   a. get siteId and server URL from registry.    -   b. already has password (may or may not be pending) so no need        to perform pending paid key request.    -   c. make connectInfo request to get xmpp server.    -   d. connect over xmpp with password.        Xmpp Connect with Password    -   a. xmpp user is of the form [serial]@[server]/[siteId]    -   b. session server performs authentication by making passthrough        API request to gateway for given SiteId.    -   c. Session xmpp server authenticates new session using DeviceKey        received in GET request against received xmpp client credential.    -   d. If authencation fails or GET receives non-response, server        returns to camera XMPP connect retry backoff with long backoff.    -   e. gateway device performs password management.    -   f. compares password with current key and pending key (if not        expired); if matches pending, then update        device-auth/session-key to be pending value, and clear out the        device-auth/pending-expiry.    -   g. gateway device updates the device/connection-status point to        reflect that camera is connected.    -   h. gateway device tracks the xmpp session server this camera is        connected to via new point device/proxy-host and updates this        info if changed.    -   i. if deviceConnected returns message, then session server posts        connected event containing xmpp user to queue monitored by all        session servers.    -   j. session servers monitor these events and disconnect/cleanup        sessions they have for same user.    -   k. may use new API endpoint on session server for broadcast        messages.        Xmpp Connect with Bad Password    -   a. Upon receiving a new connection request, session server        performs authentication by making passthrough API request to        gateway for given SiteId.    -   b. Session xmpp server authenticates new session using DeviceKey        received in above GET request against received xmpp client        credential.    -   c. If authencation fails or GET receives non-response from        virtual gateway.    -   d. Session server rejects incoming connection (is there a        backoff/retry XMPP response that can be sent here).    -   e. Session server logs event.    -   f. Gateway logs event.        Xmpp Disconnect    -   a. session server posts disconnected event to gateway (with        session server name).    -   b. gateway updates the device/connected variable/point to        reflect that camera is disconnected.    -   c. gateway updates the device/connection-status variable/point        to reflect that camera is disconnected.    -   d. gateway clears the device/proxy-host point that contains the        session host to this camera is connected.        LWGW Shutdown    -   a. During LWGW shutdown, gateway can broadcast messages to all        XMPP servers to ensure all active XMPP sessions are gracefully        shutdown.    -   b. gateways use REST client to call URI, which will broadcast to        all XMPP servers.        To Configure Camera During Installation    -   a. applies all appropriate configuration for camera (e.g.,        resolutions, users, etc).    -   b. returns message for configuration applied, wifi test passed,        all settings taken. returns other response code with error code        description upon any failure.        To Reconfigure Wifi SSID and Key    -   a. returns message for wifi credentials set.    -   b. returns other response code with error code description upon        any failure.        API Pass-Through Handling for Gateway Fail-Over Case    -   a. When performing passthrough for LWGW, the API endpoint        handles the LWGW failover case (e.g., when gateway is not        currently running on any session server).    -   b. passthrough functions in the following way: current session        server IP is maintained on the gateway object; server looks up        gateway object to get session IP and then sends passthrough        request to that session server; if that request returns gateway        not found message, server error message, or a network level        error (e.g., cannot route to host, etc.), if the gateway is a        LWGW then server should lookup the primary/secondary LW Gateway        group for this site; server should then send resume message to        primary, followed by rest request; if that fails, then server        send resume message to secondary followed by rest request    -   c. alternatively, passthrough functions in the following way:        rather than lookup session server IP on gateway object,        passthrough requests should be posted to a passthrough queue        that is monitored by all session servers; the session server        with the Gateway on it should consume the message (and pass it        to the appropriate gateway); the server should monitor for        expiry of these messages, and if the gateway is a LWGW then        server should lookup the primary/secondary LW Gateway group for        this site; server should then send resume message to primary,        followed by rest request; if that fails, then server send resume        message to secondary followed by rest request.

A detailed description follows for additional flows relating to thecamera tunnel of an embodiment.

Motion Detection

-   -   a. camera sends openhome motion event to session server via        xmpp.    -   b. session server posts motion event to gateway via passthrough        API.    -   c. gateway updates the camera motion variable/point to reflect        the event gateway updates the camera motion variable/point to        reflect the event        Capture Snapshot    -   a. gateway posts openhome snapshot command to session server        with camera connected.    -   b. gateway sends command including xmpp user id to xmpp command        Queue monitored by all session servers.    -   c. session server with given xmpp user id consumes command and        sends command to camera (command contains upload URL on gw        webapp).    -   d. gateway starts internal timer to check if a response is        received from camera (e.g., 5 sec wait window).    -   e. if broadcast RabbitMQ not ready, then gateway will use        device/proxy-host value to know which session server to post        command to.    -   f. session server sends command to camera (comprises upload URL        on gw webapp)    -   g. Example XML body:

<MediaUpload> <id>1321896772660</id><snapShotImageType>JPEG</snapShotImageType><gateway_url>[gatewaysyncUrl]/gw/GatewayService/SPutJpg/s/[siteId]/[deviceIndex]/[varValue]/[varIndex]/[who]/[ts]/[HMM]/[passCheck]/</<failure_url>[gatewaysyncUrl]/gw/GatewayService/SPutJpgError/s/[siteId]/[deviceIndex]/[varValue]/[varIndex]/[who]/[ts]/[HMM]/[passCheck]/</</MediaUpload>

-   -   h. session server receives response to sendRequestEvent from        camera and posts response to gateway.    -   i. camera uploads to upload URL on gw webapp.    -   j. passCheck can be verified on server (based upon gateway        secret); alternatively, the OpenHome spec calls for Digest Auth        here.    -   k. endpoint responds with message digest password if the URI is        expected, otherwise returns non-response.    -   l. gw webapp stores snapshot, logs history event.    -   m. event is posted to gateway for deltas.        Capture Clip    -   a. gateway posts openhome video clip capture command to session        server with camera connected.    -   b. gateway sends command including xmpp user id to xmpp command        Queue monitored by all session servers.    -   c. session server with given xmpp user id consumes command and        sends command to camera (command comprises upload URL on gw        webapp).    -   d. gateway starts internal timer to check if a response is        received from camera (e.g., 5 sec wait window).    -   e. session server sends command to camera (comprises upload URL        on gw webapp).    -   f. Example URI from session server to camera:        /openhome/streaming/channels/1/video/upload    -   g. Example XML body:

<MediaUpload> <id>1321898092270</id><videoClipFormatType>MP4</videoClipFormatType><gateway_url>[gatewaysyncUrl]/gw/GatewayService/SPutMpeg/s/[siteId]/[deviceIndex]/[varValue]/[varIndex]/[who]/[ts]/[HMM]/[passCheck]/</<failure_url>[gatewaysyncUrl]/gw/GatewayService/SPutMpegFailed/s/[siteId]/[deviceIndex]/[varValue]/[varIndex]/[who]/[ts]/[HMM]/[passCheck]/</ </MediaUpload>

-   -   h. session server receives response to sendRequestEvent from        camera and posts response to gateway.    -   i. camera uploads to upload URL on gw webapp.    -   j. passCheck can be verified on server (based upon gateway        secret).    -   k. alternatively, spec calls for Digest Auth here.    -   l. endpoint responds with message digest password if the URI is        expected, otherwise returns non-response.    -   m. gw webapp stores video clip, logs history event.    -   n. event is posted to gateway for deltas.        Live Video (Relay)    -   a. Upon user login to portal, portal creates a media relay        tunnel by calling relayAPImanager create.    -   b. RelayAPImanager creates relays and sends ip-config-relay        variable (which instructs gateway to create media tunnel) to        gateway.    -   c. Upon receiving media tunnel create ip-config-relay command,        gateway posts openhome media channel create command to session        server with camera connected.    -   d. session server sends create media tunnel command to camera        (comprises camera relay URL on relay server).    -   e. Example URI from session server to camera:        /openhome/streaming/mediatunnel/create    -   f. Example XML body:

<CreateMediaTunnel> <sessionID>1</sessionID><gatewayURL>TBD</gatewayURL> <failureURL>TBD</failureURL></CreateMediaTunnel>

-   -   g. GatewayURL is created from relay server, port, and sessionId        info included within ip-config-relay variable.    -   h. camera creates a TLS tunnel to relay server via POST to        <gatewayURL>.    -   i. When user initiates live video, portal determines user is        remote and retrieves URL of Relay server from relayAPImanager.    -   j. Upon receiving a user pole connection on the relay server        (along with valid rtsp request), relay sends streaming command        to camera: example: rtsp:://openhome/streaming/channels/1/rtsp    -   k. Upon user portal logout, portals calls relayAPImanager to        terminate media tunnel.    -   l. RelayAPImanager send ip-config-relay variable to terminate        media tunnel.    -   m. Gateway sends destroy media tunnel command to camera via        XMPP.        Camera Firmware Update    -   a. Gateway checks camera firmware version; if below minimum        version, gateway sends command to camera (via session server) to        upgrade firmware (command: /openhome/system/updatefirmware).    -   b. Gateway checks firmware update status by polling:        /openhome/system/updatefirmware/status.    -   c. Gateway informs portal of upgrade status.    -   d. Camera auto-reboots after firmware update and reconnects to        Session server.        Camera First-Contact Configuration    -   a. After a camera is added successfully and is connected to the        session server for the first time, gateway performs first        contact configuration as follows.    -   b. Check firmware version.    -   c. Configure settings by: download config file using        -   /openhome/sysetm/configurationData/configFile; or configure            each category individually (configure video input channel            settings—        -   /openhome/system/video/inputs/channels; onfigure audio input            channel settings (if            any)—/openhome/system/audio/inputs/channels; configure video            streaming channel settings—/openhome/streaming/channels;            configure motion detection settings—example: PUT            /openhome/custom/motiondetection/pir/0; configure event            trigger settings—example: PUT /openhome/custom/event).    -   d. Reboot camera (/openhome/system/factoryreset) if camera        responds with reboot required.

Embodiments include a system comprising premises equipment comprising aplurality of premises devices located at a premises. The system includesa partner device located at the premises and configured to use a partnerprotocol different from a protocol of the premises equipment. The systemincludes a system server configured to interact with the plurality ofpremises devices and the partner device. The system includes a userinterface coupled to the system server and configured to interact withthe plurality of premises devices. The user interface includes a partneruser interface corresponding to the partner device. The partner userinterface configures the user interface to interact with the partnerdevice. The user interface is configured to control interactions betweenthe plurality of premises devices and the partner device.

Embodiments include a system comprising: premises equipment comprising aplurality of premises devices located at a premises; a partner devicelocated at the premises and configured to use a partner protocoldifferent from a protocol of the premises equipment; a system serverconfigured to interact with the plurality of premises devices and thepartner device; a user interface coupled to the system server andconfigured to interact with the plurality of premises devices, whereinthe user interface includes a partner user interface corresponding tothe partner device, wherein the partner user interface configures theuser interface to interact with the partner device, wherein the userinterface is configured to control interactions between the plurality ofpremises devices and the partner device.

Embodiments include a system comprising premises equipment comprising aplurality of premises devices located at a premises. The premisesequipment corresponds to a service provider. The system includes apartner device located at the premises and configured to use a partnerprotocol different from a protocol of the premises equipment. The systemincludes a system server configured to interact with the plurality ofpremises devices. The system server is configured to interact with thepartner device via a partner proxy corresponding to the partner device.The system includes a user interface coupled to the system server andconfigured to interact with the plurality of premises devices. The userinterface includes a partner user interface corresponding to the partnerdevice. The partner user interface configures the user interface tointeract with the partner device.

Embodiments include a system comprising: premises equipment comprising aplurality of premises devices located at a premises, wherein thepremises equipment corresponds to a service provider; a partner devicelocated at the premises and configured to use a partner protocoldifferent from a protocol of the premises equipment; a system serverconfigured to interact with the plurality of premises devices, whereinthe system server is configured to interact with the partner device viaa partner proxy corresponding to the partner device; a user interfacecoupled to the system server and configured to interact with theplurality of premises devices, wherein the user interface includes apartner user interface corresponding to the partner device, wherein thepartner user interface configures the user interface to interact withthe partner device.

The partner proxy is configured to interact with a partner server andthe partner device, wherein the partner server corresponds to thepartner device and the partner proxy.

The partner device at least one of controls and triggers automations inthe plurality of premises devices via the partner server.

The system server is configured to include the partner proxy and tocommunicate with the partner server via the partner proxy.

The partner proxy is configured to proxy calls from the partner userinterface to the partner server.

The partner user interface is embedded in the user interface.

The system includes an integration server coupled to the system server.

The system server includes an integration application programminginterface (API).

The integration server is coupled to the integration API.

The system includes an event bus coupled to the system server and theintegration server.

The integration server is coupled to the partner server.

The system includes an integration adapter coupled to the integrationserver.

The integration adapter is configured to translate between protocols ofthe system server and the partner server.

The integration adapter is coupled to the partner server.

The integration adapter is configured to provide endpoints forassociating with the partner device.

The integration adapter is configured to process events coming from theintegration server, wherein the events comprise device datacorresponding to the partner device.

The device data includes at least one of state data, control data, andcommand data.

The integration adapter is configured to send events to the integrationserver.

The integration adapter is configured to send events includingacknowledgment of incoming system events.

The integration adapter is configured as an endpoint for managed partnerdevice events to be reported to the system server.

The system includes a rules engine.

The rules engine is configured to run on the premises equipment.

The rules engine is configured to run on the system server.

The rules engine is configured to run on at least one of the systemserver and the premises equipment.

The system includes automation rules running on the rules engine,wherein the automation rules include actions and triggers forcontrolling interactions between at least one of the partner device andthe plurality of premises devices.

The rules engine is configured to treat an event relating to the partnerdevice as a trigger for at least one rule.

In response to the event the at least one rule triggers at least oneaction event to at least one of the partner device, at least one otherpartner device, and at least one of the plurality of devices.

The partner user interface is configured to at least one of create andedit at least one rule of the automation rules.

The partner user interface is configured to delete at least one rule ofthe automation rules.

The partner user interface includes a list comprising a plurality ofpartners, wherein the plurality of partners correspond to a plurality ofpartner devices.

The partner user interface is configured with partner data of thepartner device received from the system server in response to selectionof a corresponding partner from the plurality of partners.

The partner user interface is configured to authenticate with thepartner server a user corresponding to the partner device.

The system server is configured with information of the partner deviceas a result of authentication of the user.

The partner user interface interacts with the partner server via thepartner proxy. The partner user interface receives data relating to thepartner device from the partner server.

The system includes an integration descriptor, wherein the integrationdescriptor includes capabilities data of the partner device.

The capabilities data includes at least one of attributes, actions,events, and associated parameters of the partner device.

The integration descriptor is configured for use to provide access tocapabilities of the system server.

The system includes a rules template file including a description ofavailable functionality of at least one of the plurality of premisesdevices and the partner device.

The system includes a card user interface coupled to the system server,wherein the card user interface includes UI elements in a card-likeconfiguration and configured to generate the partner user interface.

Embodiments include a method comprising configuring a system server tointeract with premises equipment comprising a plurality of premisesdevices located at a premises. The premises equipment corresponds to aservice provider. The method includes configuring the system server tointeract with a partner device at the premises via a partner proxycorresponding to the partner device. The partner device is configured touse a partner protocol different from a protocol of the premisesequipment. The method includes configuring a user interface to interactwith the plurality of premises devices. The user interface includes apartner user interface corresponding to the partner device. The partneruser interface configures the user interface to interact with thepartner device.

Embodiments include a method comprising: configuring a system server tointeract with premises equipment comprising a plurality of premisesdevices located at a premises, wherein the premises equipmentcorresponds to a service provider; configuring the system server tointeract with a partner device at the premises via a partner proxycorresponding to the partner device, wherein the partner device isconfigured to use a partner protocol different from a protocol of thepremises equipment; configuring a user interface to interact with theplurality of premises devices, wherein the user interface includes apartner user interface corresponding to the partner device, wherein thepartner user interface configures the user interface to interact withthe partner device.

The method includes configuring the partner proxy to interact with apartner server and the partner device, wherein the partner servercorresponds to the partner device and the partner proxy.

The method includes configuring the partner device to at least one ofcontrol and trigger automations in the plurality of premises devices viathe partner server.

The method includes configuring the system server to include the partnerproxy and to communicate with the partner server via the partner proxy.

The method includes configuring the partner proxy to proxy calls fromthe partner user interface to the partner server.

The method includes embedding the partner user interface in the userinterface.

The method includes configuring an integration server to communicatewith the system server.

The method includes configuring the system server to include anintegration application programming interface (API).

The integration server is coupled to the integration API.

The integration server is coupled to the partner server.

The method includes configuring an integration adapter to communicatewith the integration server.

The method includes configuring the integration adapter to translatebetween protocols of the system server and the partner server.

The method includes configuring the integration adapter to communicatewith the partner server.

The method includes configuring the integration adapter to provideendpoints for associating with the partner device.

The method includes configuring the integration adapter to processevents coming from the integration server, wherein the events comprisedevice data corresponding to the partner device.

The device data includes at least one of state data, control data, andcommand data.

The method includes configuring the integration adapter to send eventsto the integration server.

The method includes configuring the integration adapter to send eventsincluding acknowledgment of incoming system events.

The method includes configuring the integration adapter as an endpointfor managed partner device events to be reported to the system server.

The method includes configuring a rules engine to run on at least one ofthe system server and the premises equipment.

The method includes configuring the rules engine to run on the premisesequipment.

The method includes configuring the rules engine to run on the systemserver.

The method includes configuring automation rules to execute on the rulesengine, wherein the automation rules include actions and triggers forcontrolling interactions between at least one of the partner device andthe plurality of premises devices.

The method includes configuring the rules engine to treat an eventrelating to the partner device as a trigger for at least one rule.

The method includes, in response to the event, triggering with the atleast one rule at least one action event to at least one of the partnerdevice, at least one other partner device, and at least one of theplurality of devices.

The method includes configuring the partner user interface to at leastone of create and edit at least one rule of the automation rules.

The method includes configuring the partner user interface to delete atleast one rule of the automation rules.

The method includes configuring the partner user interface to include alist comprising a plurality of partners, wherein the plurality ofpartners correspond to a plurality of partner devices.

The method includes configuring the partner user interface to includepartner data of the partner device received from the system server inresponse to selection of a corresponding partner from the plurality ofpartners.

The method includes configuring the partner user interface toauthenticate with the partner server a user corresponding to the partnerdevice.

The method includes configuring the system server with information ofthe partner device as a result of authentication of the user.

The method includes configuring the partner user interface to interactwith the partner server via the partner proxy.

The method includes configuring the partner user interface to receivedata relating to the partner device from the partner server.

The method includes configuring an integration descriptor to includecapabilities data of the partner device.

The capabilities data includes at least one of attributes, actions,events, and associated parameters of the partner device.

The method includes configuring the integration descriptor for use toprovide access to capabilities of the system server.

The method includes configuring a rules template file to include adescription of available functionality of at least one of the pluralityof premises devices and the partner device.

Embodiments include a system comprising premises equipment comprising aplurality of premises devices located at a premises. The premisesequipment corresponds to a service provider. The system includes apartner device located at the premises and configured to use a partnerprotocol different from a protocol of the premises equipment. The systemincludes a system server configured to interact with the plurality ofpremises devices. The system server is configured to interact with thepartner device via a partner proxy corresponding to the partner device.The system includes automation rules coupled to the system server. Theautomation rules include actions and triggers for controllinginteractions between at least one of the partner device and theplurality of premises devices. The system includes a user interfacecoupled to the system server and configured to interact with theplurality of premises devices and the partner device.

Embodiments include a system comprising: premises equipment comprising aplurality of premises devices located at a premises, wherein thepremises equipment corresponds to a service provider; a partner devicelocated at the premises and configured to use a partner protocoldifferent from a protocol of the premises equipment; a system serverconfigured to interact with the plurality of premises devices, whereinthe system server is configured to interact with the partner device viaa partner proxy corresponding to the partner device; automation rulescoupled to the system server, wherein the automation rules includeactions and triggers for controlling interactions between at least oneof the partner device and the plurality of premises devices; a userinterface coupled to the system server and configured to interact withthe plurality of premises devices and the partner device.

The user interface includes a partner user interface corresponding tothe partner device, wherein the partner user interface configures theuser interface to interact with the partner device.

The partner user interface is configured to at least one of create andedit at least one rule of the automation rules.

The partner user interface is configured to delete at least one rule ofthe automation rules.

The partner proxy is configured to interact with a partner server andthe partner device, wherein the partner server corresponds to thepartner device and the partner proxy.

The partner device at least one of controls and triggers automations inthe plurality of premises devices via the partner server.

The system server is configured to include the partner proxy and tocommunicate with the partner server via the partner proxy.

The partner proxy is configured to proxy calls from the partner userinterface to the partner server.

The partner user interface is embedded in the user interface.

The system includes an integration server coupled to the system server.

The system server includes an integration application programminginterface (API).

The integration server is coupled to the integration API.

The system includes an event bus coupled to the system server and theintegration server.

The integration server is coupled to the partner server.

The system includes an integration adapter coupled to the integrationserver.

The integration adapter is configured to translate between protocols ofthe system server and the partner server.

The integration adapter is coupled to the partner server.

The integration adapter is configured to provide endpoints forassociating with the partner device.

The integration adapter is configured to process events coming from theintegration server, wherein the events comprise device datacorresponding to the partner device.

The device data includes at least one of state data, control data, andcommand data.

The integration adapter is configured to send events to the integrationserver.

The integration adapter is configured to send events includingacknowledgment of incoming system events.

The integration adapter is configured as an endpoint for managed partnerdevice events to be reported to the system server.

The system includes a rules engine configured to run the automationrules.

The rules engine is configured to run on the premises equipment.

The rules engine is configured to run on the system server.

The rules engine is configured to run on at least one of the systemserver and the premises equipment.

The rules engine is configured to treat an event relating to the partnerdevice as a trigger for at least one rule.

In response to the event the at least one rule triggers at least oneaction event to at least one of the partner device, at least one otherpartner device, and at least one of the plurality of devices.

The partner user interface includes a list comprising a plurality ofpartners, wherein the plurality of partners corresponds to a pluralityof partner devices.

The partner user interface is configured with partner data of thepartner device received from the system server in response to selectionof a corresponding partner from the plurality of partners.

The partner user interface is configured to authenticate with thepartner server a user corresponding to the partner device.

The system server is configured with information of the partner deviceas a result of authentication of the user.

The partner user interface interacts with the partner server via thepartner proxy.

The partner user interface receives data relating to the partner devicefrom the partner server.

The system includes an integration descriptor that includes capabilitiesdata of the partner device.

The capabilities data includes at least one of attributes, actions,events, and associated parameters of the partner device.

The integration descriptor is configured for use to provide access tocapabilities of the system server.

The system includes a rules template file including a description ofavailable functionality of at least one of the plurality of premisesdevices and the partner device.

Embodiments include a method comprising configuring a system server tointeract with premises equipment including a plurality of premisesdevices located at the premises. The premises equipment corresponds to aservice provider. The method includes configuring the system server tointeract with a partner device at the premises via a partner proxycorresponding to the partner device. The partner device is configured touse a partner protocol different from a protocol of the premisesequipment. The method includes configuring automation rules to controlinteractions between at least one of the partner device and theplurality of premises devices using actions and triggers. The methodincludes configuring a user interface coupled to the system server tointeract with the plurality of premises devices and the partner device.

Embodiments include a method comprising: configuring a system server tointeract with premises equipment including a plurality of premisesdevices located at the premises, wherein the premises equipmentcorresponds to a service provider; configuring the system server tointeract with a partner device at the premises via a partner proxycorresponding to the partner device, wherein the partner device isconfigured to use a partner protocol different from a protocol of thepremises equipment; configuring automation rules to control interactionsbetween at least one of the partner device and the plurality of premisesdevices using actions and triggers; configuring a user interface coupledto the system server to interact with the plurality of premises devicesand the partner device.

The method includes configuring the user interface to include a partneruser interface corresponding to the partner device, wherein the partneruser interface configures the user interface to interact with thepartner device.

The method includes configuring the partner user interface to at leastone of create and edit at least one rule of the automation rules.

The method includes configuring the partner user interface to delete atleast one rule of the automation rules.

The method includes configuring the partner proxy to interact with apartner server and the partner device, wherein the partner servercorresponds to the partner device and the partner proxy.

The method includes configuring the partner device to at least one ofcontrol and trigger automations in the plurality of premises devices viathe partner server.

The method includes configuring the system server to include the partnerproxy and to communicate with the partner server via the partner proxy.

The method includes configuring the partner proxy to proxy calls fromthe partner user interface to the partner server.

The method includes embedding the partner user interface in the userinterface.

The method includes configuring an integration server to communicatewith the system server.

The method includes configuring the system server to include anintegration application programming interface (API).

The method includes configuring the integration server to communicatewith the integration API.

The method includes configuring an event bus to communicate with thesystem server and the integration server.

The method includes configuring the integration server to communicatewith the partner server.

The method includes configuring the integration server to communicatewith an integration adapter.

The integration adapter is configured to translate between protocols ofthe system server and the partner server.

The integration adapter is coupled to the partner server.

The integration adapter is configured to provide endpoints forassociating with the partner device.

The integration adapter is configured to process events coming from theintegration server, wherein the events comprise device datacorresponding to the partner device.

The device data includes at least one of state data, control data, andcommand data.

The integration adapter is configured to send events to the integrationserver.

The integration adapter is configured to send events includingacknowledgment of incoming system events.

The integration adapter is configured as an endpoint for managed partnerdevice events to be reported to the system server.

The method includes configuring a rules engine to run the automationrules.

The method includes configuring the rules engine to run on the premisesequipment.

The method includes configuring the rules engine to run on the systemserver.

The method includes configuring the rules engine to run on at least oneof the system server and the premises equipment.

The method includes configuring the rules engine to treat an eventrelating to the partner device as a trigger for at least one rule.

The method includes, in response to the event, triggering with the atleast one rule at least one action event to at least one of the partnerdevice, at least one other partner device, and at least one of theplurality of devices.

The method includes configuring the partner user interface to include alist comprising a plurality of partners, wherein the plurality ofpartners correspond to a plurality of partner devices.

The method includes configuring the partner user interface with partnerdata of the partner device received from the system server in responseto selection of a corresponding partner from the plurality of partners.

The method includes configuring the partner user interface toauthenticate with the partner server a user corresponding to the partnerdevice.

The method includes configuring the system server with information ofthe partner device as a result of authentication of the user.

The method includes configuring the partner user interface to interactwith the partner server via the partner proxy.

The method includes configuring the partner user interface to receivedata relating to the partner device from the partner server.

The method includes configuring an integration descriptor to includecapabilities data of the partner device.

The capabilities data includes at least one of attributes, actions,events, and associated parameters of the partner device.

The method includes configuring the integration descriptor for use toprovide access to capabilities of the system server.

The method includes configuring a rules template file to include adescription of available functionality of at least one of the pluralityof premises devices and the partner device.

As described above, computer networks suitable for use with theembodiments described herein include local area networks (LAN), widearea networks (WAN), Internet, or other connection services and networkvariations such as the world wide web, the public internet, a privateinternet, a private computer network, a public network, a mobilenetwork, a cellular network, a value-added network, and the like.Computing devices coupled or connected to the network may be anymicroprocessor controlled device that permits access to the network,including terminal devices, such as personal computers, workstations,servers, mini computers, main-frame computers, laptop computers, mobilecomputers, palm top computers, hand held computers, mobile phones, TVset-top boxes, or combinations thereof. The computer network may includeone of more LANs, WANs, Internets, and computers. The computers mayserve as servers, clients, or a combination thereof

The system can be a component of a single system, multiple systems,and/or geographically separate systems. The system can also be asubcomponent or subsystem of a single system, multiple systems, and/orgeographically separate systems. The system can be coupled to one ormore other components (not shown) of a host system or a system coupledto the host system.

One or more components of the system and/or a corresponding system orapplication to which the system is coupled or connected includes and/orruns under and/or in association with a processing system. Theprocessing system includes any collection of processor-based devices orcomputing devices operating together, or components of processingsystems or devices, as is known in the art. For example, the processingsystem can include one or more of a portable computer, portablecommunication device operating in a communication network, and/or anetwork server. The portable computer can be any of a number and/orcombination of devices selected from among personal computers, personaldigital assistants, portable computing devices, and portablecommunication devices, but is not so limited. The processing system caninclude components within a larger computer system.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that includes the system herein can belocated together or in separate locations. Communication paths couplethe components and include any medium for communicating or transferringfiles among the components. The communication paths include wirelessconnections, wired connections, and hybrid wireless/wired connections.The communication paths also include couplings or connections tonetworks including local area networks (LANs), metropolitan areanetworks (MANs), wide area networks (WANs), proprietary networks,interoffice or backend networks, and the Internet. Furthermore, thecommunication paths include removable fixed mediums like floppy disks,hard disk drives, and CD-ROM disks, as well as flash RAM, UniversalSerial Bus (USB) connections, RS-232 connections, telephone lines,buses, and electronic mail messages.

Aspects of the systems and methods described herein may be implementedas functionality programmed into any of a variety of circuitry,including programmable logic devices (PLDs), such as field programmablegate arrays (FPGAs), programmable array logic (PAL) devices,electrically programmable logic and memory devices and standardcell-based devices, as well as application specific integrated circuits(ASICs). Some other possibilities for implementing aspects of thesystems and methods include: microcontrollers with memory (such aselectronically erasable programmable read only memory (EEPROM)),embedded microprocessors, firmware, software, etc. Furthermore, aspectsof the systems and methods may be embodied in microprocessors havingsoftware-based circuit emulation, discrete logic (sequential andcombinatorial), custom devices, fuzzy (neural) logic, quantum devices,and hybrids of any of the above device types. Of course the underlyingdevice technologies may be provided in a variety of component types,e.g., metal-oxide semiconductor field-effect transistor (MOSFET)technologies like complementary metal-oxide semiconductor (CMOS),bipolar technologies like emitter-coupled logic (ECL), polymertechnologies (e.g., silicon-conjugated polymer and metal-conjugatedpolymer-metal structures), mixed analog and digital, etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the systems and methods is notintended to be exhaustive or to limit the systems and methods to theprecise forms disclosed. While specific embodiments of, and examplesfor, the systems and methods are described herein for illustrativepurposes, various equivalent modifications are possible within the scopeof the systems and methods, as those skilled in the relevant art willrecognize. The teachings of the systems and methods provided herein canbe applied to other systems and methods, not only for the systems andmethods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the systems and methods in light of the above detaileddescription.

What is claimed is:
 1. A system comprising: a plurality of premises devices located at a premises, wherein the plurality of premises devices comprises at least one thermostat; and a gateway device, located at the premises, configured to: communicate with the plurality of premises devices, receive an indication of an event associated with a weather data service that is not configured to communicate with the gateway device, and cause, based on the indication of the event and at least one automation rule of a plurality of automation rules, one or more actions of the at least one thermostat.
 2. The system of claim 1, further comprising: a server, located external to the premises, configured to: determine the event associated with the weather data service; and send to the gateway device, the indication of the event.
 3. The system of claim 2, further comprising an integration server configured to communicate with the server.
 4. The system of claim 3, wherein the server comprises an integration application programming interface (API), and wherein the integration server is configured to communicate with the integration API.
 5. The system of claim 3, comprising a bus configured to communicate with the server and the integration server.
 6. The system of claim 3, comprising an integration adapter configured to communicate with the integration server.
 7. The system of claim 3, comprising an integration adapter configured to communicate with the integration server, wherein the integration adapter is configured to translate between protocols of the server and another device.
 8. The system of claim 3, comprising an integration adapter configured to communicate with the integration server, wherein the integration adapter is configured to provide endpoints to associate with the gateway device.
 9. The system of claim 3, comprising an integration adapter configured to communicate with the integration server, wherein the integration adapter is configured to process one or more events received from the integration server, wherein the events comprise device data corresponding to the weather data service.
 10. The system of claim 3, comprising an integration adapter configured to communicate with the integration server, wherein the integration adapter is configured to process one or more events received from the integration server, wherein the events comprise device data corresponding to the weather data service, and wherein the device data comprises at least one of state data, control data, or command data.
 11. The system of claim 3, comprising an integration adapter configured to communicate with the integration server, wherein the integration adapter is configured to transmit events to the integration server.
 12. The system of claim 3, comprising an integration adapter configured to communicate with the integration server, wherein the integration adapter is configured to transmit events comprising acknowledgment of incoming system events.
 13. The system of claim 3, comprising an integration adapter configured to communicate with the integration server, wherein the integration adapter is configured as an endpoint for managed device events to be reported to the server.
 14. The system of claim 2, wherein the server comprises an integration application programming interface (API).
 15. The system of claim 2, comprising a rules engine.
 16. The system of claim 15, wherein the rules engine is configured to execute on at least one the server or the gateway device.
 17. The system of claim 15, wherein the rules engine is configured to execute on at least one of the server or the gateway device.
 18. The system of claim 15, further comprising automation rules executing on the rules engine, wherein the automation rules comprise actions and triggers configured to control interactions between at least one of the gateway device or the plurality of premises devices.
 19. The system of claim 15, wherein the rules engine is configured to treat an event associated with the weather data service as a trigger for at least one rule.
 20. The system of claim 15, wherein the rules engine is configured to treat an event associated with the weather data service as a trigger for at least one rule, wherein in response to the event the at least one rule triggers at least one action event to at least one of the gateway device, at least one other device, or at least one of the plurality of premises devices.
 21. The system of claim 15, further comprising automation rules executing on the rules engine, wherein the automation rules comprise actions and triggers configured to control interactions between at least one of the gateway device or the plurality of premises devices, wherein the user interface is configured to at least one of create or edit at least one rule of the automation rules.
 22. The system of claim 15, further comprising automation rules executing on the rules engine, wherein the automation rules comprise actions and triggers configured to control interactions between at least one of the gateway device or the plurality of premises devices, wherein the user interface is configured to delete at least one rule of the automation rules.
 23. The system of claim 2, wherein the user interface is configured to authenticate with the server a user corresponding to the gateway device.
 24. The system of claim 23, wherein the server is configured with information of the gateway device as a result of authentication of the user.
 25. The system of claim 2, wherein the user interface is configured to communicate with the server.
 26. The system of claim 2, wherein the user interface is configured to receive data associated with the gateway device from the server.
 27. The system of claim 2, wherein the server is configured to store an integration descriptor, wherein the integration descriptor comprises capabilities data of the gateway device.
 28. The system of claim 27, wherein the capabilities data comprises at least one of attributes, actions, events, or associated parameters of the gateway device.
 29. The system of claim 27, wherein the integration descriptor is configured to enable access to capabilities of the server.
 30. The system of claim 27, wherein the server is configured to store, in a rules template file, a description of available functionality of at least one of the plurality of premises devices or the gateway device.
 31. The system of claim 1, further comprising: a computing device configured to communicate with the gateway device, wherein the computing device comprises a user interface configured to enable user configuration of the plurality of automation rules.
 32. The system of claim 1, wherein the gateway device is configured to at least one of control or trigger automations in the plurality of premises devices.
 33. The system of claim 31, wherein the computing device comprises a touchscreen device.
 34. A method comprising: communicating, by a gateway device located at a premises, with a plurality of premises devices located at the premises, wherein the plurality of premises devices comprises at least one thermostat; receiving, by the gateway device, an indication of an event associated with a weather data service that is not configured to communicate with the gateway device; and causing, based on the indication of the event and at least one automation rule of a plurality of automation rules, one or more actions of the at least one thermostat.
 35. The method of claim 34, further comprising: determining, by a server located external to the premises, the event associated with the weather data service; and sending, by the server, to the gateway device, the indication of the event.
 36. The method of claim 35, further comprising controlling or triggering, by the gateway device, automations in the plurality of premises devices via the server.
 37. The method of claim 34, further comprising communicating, by the gateway device, with a computing device comprising a user interface configured to enable user configuration of the plurality of automation rules.
 38. The method of claim 35, further comprising proxying calls, by the computing device, from the user interface to the server.
 39. The method of claim 35, wherein an integration server is configured to communicate with the server.
 40. The method of claim 35, wherein the server comprises an integration application programming interface (API).
 41. The method of claim 39, wherein the server comprises an integration application programming interface (API), and wherein the integration server is configured to communicate with the integration API.
 42. The method of claim 37, wherein the computing device comprises a touchscreen device.
 43. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server.
 44. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server and the method further comprising translating, by the integration adapter, between protocols of the server and another device.
 45. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server, and wherein the integration adapter is configured to communicate with the server.
 46. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server, and the method further comprising providing, by the integration adapter, endpoints to associate with the gateway device.
 47. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server, and the method further comprising processing, by the integration adapter, one or more events received from the integration server, wherein the events comprise device data associated with the weather data service.
 48. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server, and the method further comprising: processing, by the integration adapter, one or more events received from the integration server, wherein the events comprise device data associated with the weather data service, wherein the device data comprises at least one of state data, control data, or command data.
 49. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server, and the method further comprising transmitting, by the integration adapter, events to the integration server.
 50. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server, and the method further comprising transmitting, by the integration adapter, events comprising acknowledgment of incoming system events.
 51. The method of claim 39, wherein an integration adapter is configured to communicate with the integration server, and the method further comprising managing device events, by the integration adapter as an endpoint, to be reported to the server.
 52. The method of claim 35, further comprising generating a rules engine to execute on at least one of the server or the gateway device.
 53. The method of claim 35, further comprising generating a rules engine to execute on the server.
 54. The method of claim 52, further comprising generating automation rules to execute on the rules engine, wherein the automation rules comprise actions and triggers configured to control communications between at least one of the gateway device or the plurality of premises devices.
 55. The method of claim 52, wherein the rules engine is configured to treat an event associated with the device as a trigger for at least one rule.
 56. The method of claim 52, wherein the rules engine is configured to treat an event associated with the device as a trigger for at least one rule, and the method further comprising: in response to the event, triggering with the at least one rule at least one action event to at least one of the gateway device, at least one other device, or at least one of the plurality of premises devices.
 57. The method of claim 52, further comprising: generating automation rules to execute on the rules engine, wherein the automation rules comprise actions and triggers configured to control communications between at least one of the gateway device or the plurality of premises devices; and creating or editing, by the user interface, at least one rule of the automation rules.
 58. The method of claim 52, further comprising: generating automation rules to execute on the rules engine, wherein the automation rules comprise actions and triggers configured to control communications between at least one of the gateway device or the plurality of premises devices; and deleting, by the user interface, at least one rule of the automation rules.
 59. The method of claim 35, further comprising authenticating, by the user interface, a user with the server, wherein the user is associated with the gateway device.
 60. The method of claim 59, further comprising providing, by the server, information associated with the gateway device as a result of authentication of the user.
 61. The method of claim 35, wherein the user interface is configured to communicate with the server.
 62. The method of claim 61, further comprising receiving, by the user interface, data associated with the gateway device from the server.
 63. The method of claim 35, further comprising generating an integration descriptor to comprise capabilities data of the gateway device.
 64. The method of claim 63, wherein the capabilities data comprises at least one of attributes, actions, events, or associated parameters of the gateway device.
 65. The method of claim 63, further comprising providing, by the integration descriptor, access to capabilities of the server.
 66. The method of claim 63, further comprising generating a rules template file to comprise a description of available functionality of at least one of the plurality of premises devices or the gateway device.
 67. The system of claim 1, wherein the gateway device is configured to at least one of control or trigger automations in at least one of the plurality of premises devices.
 68. The system of claim 1, wherein the gateway device is configured to communicate with the premises devices via a communication protocol, and wherein the weather data service is not configured to communicate via the communication protocol.
 69. The system of claim 1, wherein the weather data service is not configured to establish a communication session with the gateway.
 70. The system of claim 1, wherein the event comprises at least one of a current temperature, current precipitation conditions, a daily high temperature, a daily low temperature, a daily precipitation forecast, or a severe weather alert. 